Balthazar wiki_balthazar https://balthazar.space/wiki/Main_Page MediaWiki 1.33.0 first-letter Media Special Talk User User talk Balthazar Balthazar talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Gadget Gadget talk Gadget definition Gadget definition talk 0 1 1 2019-08-26T15:12:00Z MediaWiki default 0 wikitext text/x-wiki <strong>MediaWiki has been installed.</strong> Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki] 5702e4d5fd9173246331a889294caf01a3ad3706 3 1 2019-08-27T07:25:34Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet. Secure, fast, inexpensive. Pick all three.</strong> === BPCD - Balthazar Personal Computing Device is a 13.3" laptop that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows GNU, FOSS and EOMA guidelines. === ==== It is very expensive to buy an “advanced” or secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in. BPCD is aimed to inexpensively enable end user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded by any 3rd party. It is NOT OLPC-like, but it follows some of OLPC product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. ==== === Remember - a “Cloud” is just other people’s or corporations’  computers. ===   ==== Education being a very important issue today all over the planet is yet another field where BPCD will make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX) ==== 6a633d23adf85e0f98bce49c57efed67c3ab86d1 4 3 2019-08-27T07:27:52Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet. Secure, fast, inexpensive. Pick all three.</strong> BPCD - Balthazar Personal Computing Device is a 13.3" laptop that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows GNU, FOSS and EOMA guidelines. It is very expensive to buy an “advanced” or secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in. BPCD is aimed to inexpensively enable end user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded by any 3rd party. It is NOT OLPC-like, but it follows some of OLPC product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. === Remember - a “Cloud” is just other people’s or corporations’  computers. ===   Education being a very important issue today all over the planet is yet another field where BPCD will make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.) 2a38a6bea5bc78a9eeea44adb789d5e279a77123 5 4 2019-08-27T07:30:27Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet.</strong> <strong>Secure, fast, inexpensive. Pick all three.</strong> BPCD - Balthazar Personal Computing Device is a 13.3" laptop that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows GNU, FOSS and EOMA guidelines. It is very expensive to buy an “advanced” or secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in. BPCD is aimed to inexpensively enable end user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded by any 3rd party. It is NOT OLPC-like, but it follows some of OLPC product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. === Remember - a “Cloud” is just other people’s or corporations’  computers. ===   Education being a very important issue today all over the planet is yet another field where BPCD will make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.) ac9f884d6fc8524f35751d62208d9b0474b47da3 7 5 2019-08-27T10:13:07Z Harv 2 /* Remember - a “Cloud” is just other people’s or corporations’  computers. */ wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet.</strong> <strong>Secure, fast, inexpensive. Pick all three.</strong> BPCD - Balthazar Personal Computing Device is a 13.3" laptop that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows GNU, FOSS and EOMA guidelines. It is very expensive to buy an “advanced” or secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in. BPCD is aimed to inexpensively enable end user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded by any 3rd party. It is NOT OLPC-like, but it follows some of OLPC product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. Remember - a “Cloud” is just other people’s or corporations’  computers. Education being a very important issue today all over the planet is yet another field where BPCD will make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.) 3c4802e00b3b6b7504d054bc48b216dedfc0fb3b 11 7 2019-08-27T11:26:51Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet.</strong> <strong>Secure, fast, inexpensive. Pick all three.</strong><br> BPCD - Balthazar Personal Computing Device is a 13.3" laptop based on RiscV processor(s) that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows CC, GNU-GPL, FOSS and EOMA guidelines.<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in at the most possible lowest price that should be available to everyone from an individual up to a large institutions.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> Google, Samsung, Acer, Dell and the other respective partners did indeed made inexpensive and lightweight laptops, but they are locked in a certain software and hardware ecosystems and actually offer not so many security features while appearing less flexible towards full FOSS, GNU-GPL and EOMA guidelines that we want to set as another standard. That ethical standard is not based on a profit, but on protecting and also educating population on how not to voluntary disseminate their data all over the interwebs, being used as a bait for large companies that take an advantage of such unconsciousness and irresponsible behaviour.<br> Also those do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> BPCD is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> It is <strong>NOT</strong> OLPC-alike, but it does follow some of OLPC product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But Cloud is cool and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data that you "share" with them. You do not really read small text, do you?<br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD will make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> More on that please read the #REDIRECT [[specifications and features]] . e4b7f89a62963a962e37429473381614a84277be 16 11 2019-08-27T12:21:14Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet.</strong> <strong>Secure, fast, inexpensive. Pick all three.</strong><br> BPCD - Balthazar Personal Computing Device is a 13.3" laptop based on RiscV processor(s) that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows CC, GNU-GPL, FOSS and EOMA guidelines.<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in at the most possible lowest price that should be available to everyone from an individual up to a large institutions.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> Google, Samsung, Acer, Dell and the other respective partners did indeed made inexpensive and lightweight laptops, but they are locked in a certain software and hardware ecosystems and actually offer not so many security features while appearing less flexible towards full FOSS, GNU-GPL and EOMA guidelines that we want to set as another standard. That ethical standard is not based on a profit, but on protecting and also educating population on how not to voluntary disseminate their data all over the interwebs, being used as a bait for large companies that take an advantage of such unconsciousness and irresponsible behaviour.<br> Also those do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> BPCD is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> It is <strong>NOT</strong> OLPC-alike, but it does follow some of OLPC product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But Cloud is cool and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data that you "share" with them. You do not really read small text, do you?<br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD will make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> More on that please read the [[specifications and features]] . 14fe95ea8cc7e00041b8f7949f170ba6f5eae3ea 20 16 2019-08-27T12:41:41Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet.</strong> <strong>Secure, fast, inexpensive. Pick all three.</strong><br> BPCD - Balthazar Personal Computing Device is a 13.3" laptop based on RiscV processor(s) that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows CC, GNU-GPL, FOSS and EOMA guidelines.<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in at the most possible lowest price that should be available to everyone from an individual up to a large institutions.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> Google, Samsung, Acer, Dell and the other respective partners did indeed made inexpensive and lightweight laptops, but they are locked in a certain software and hardware ecosystems and actually offer not so many security features while appearing less flexible towards full FOSS, GNU-GPL and EOMA guidelines that we want to set as another standard. That ethical standard is not based on a profit, but on protecting and also educating population on how not to voluntary disseminate their data all over the interwebs, being used as a bait for large companies that take an advantage of such unconsciousness and irresponsible behaviour.<br> Also those do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> BPCD is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> It is <strong>NOT</strong> OLPC-alike, but it does follow some of OLPC product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But Cloud is cool and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data that you "share" with them. <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD will make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> More on that please read the [[specifications and features]] . 6baa35f8217901f0f5bde632e9c1a83834072001 21 20 2019-08-27T12:42:17Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet.</strong> <strong>Secure, fast, inexpensive. Pick all three.</strong><br> BPCD - Balthazar Personal Computing Device is a 13.3" laptop based on RiscV processor(s) that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows CC, GNU-GPL, FOSS and EOMA guidelines.<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in at the most possible lowest price that should be available to everyone from an individual up to a large institutions.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> Google, Samsung, Acer, Dell and the other respective partners did indeed made inexpensive and lightweight laptops, but they are locked in a certain software and hardware ecosystems and actually offer not so many security features while appearing less flexible towards full FOSS, GNU-GPL and EOMA guidelines that we want to set as another standard. That ethical standard is not based on a profit, but on protecting and also educating population on how not to voluntary disseminate their data all over the interwebs, being used as a bait for large companies that take an advantage of such unconsciousness and irresponsible behaviour.<br> Also those do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> BPCD is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> It is <strong>NOT</strong> OLPC-alike, but it does follow some of OLPC product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But Cloud is cool and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data that you "share" with them.<br> <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD will make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> More on that please read the [[specifications and features]] . 5fa46a8ba4c5c991ec5aabdb1df50066419ce5ff 22 21 2019-08-27T12:59:38Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet.</strong> <strong>Secure, fast, inexpensive. Pick all three.</strong><br> BPCD - Balthazar Personal Computing Device is a 13.3" laptop based on RiscV processor(s) that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows CC, GNU-GPL, FOSS and EOMA guidelines.<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in at the most possible lowest price that should be available to everyone from an individual up to a large institutions.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> Google, Samsung, Acer, Dell and the other respective partners did indeed made inexpensive and lightweight laptops, but they are locked in a certain software and hardware ecosystems and actually offer not so many security features while appearing less flexible towards full FOSS, GNU-GPL and EOMA guidelines that we want to set as another standard. That ethical standard is not based on a profit, but on protecting and also educating population on how not to voluntary disseminate their data all over the interwebs, being used as a bait for large companies that take an advantage of such unconsciousness and irresponsible behaviour.<br> Also those do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> BPCD is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here is the answer:<br> '''1.''' An average basic internet user that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' Advanced computer users, governmental and public workers that need hardware and software features to prevent an intrusion and are skilled and aware enough so they can use all the built in hardware and software features and use additional encryption for official and personal data protection through secure productivity apps and tools.<br> '''3.''' Educational institutions that will teach online security, privacy and safety. Also that will make use of a device’s connections versatility as in hardware connectivity, as well as in software User Interface and User Expiriance utilising age adoptive “aperture Operating System” and featured secure online in-the-browser Workbench and added to it find the value in overall physical sturdiness and upgrade-ability.<br> TLDR; '''For the children age 9-99.''' <strong>Ahh, another OLPC thingy I can see upcoming, or...?</strong><br> It is <strong>NOT</strong> OLPC-alike, but it does follow some of OLPC product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is cool and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD will make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> More on that please read the [[specifications and features]] . 04d8dc825700ac59245522ca1896fe94a3b09380 23 22 2019-08-27T13:23:52Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet.</strong> <strong>Secure, fast, inexpensive. Pick all three.</strong><br> BPCD - Balthazar Personal Computing Device is a 13.3" laptop based on RiscV processor(s) that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows CC, GNU-GPL, FOSS and EOMA guidelines.<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in at the most possible lowest price that should be available to everyone from an individual up to a large institutions.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> Google, Samsung, Acer, Dell and the other respective partners did indeed made inexpensive and lightweight laptops, but they are locked in a certain software and hardware ecosystems and actually offer not so many security features while appearing less flexible towards full FOSS, GNU-GPL and EOMA guidelines that we want to set as another standard. That ethical standard is not based on a profit, but on protecting and also educating population on how not to voluntary disseminate their data all over the interwebs, being used as a bait for large companies that take an advantage of such unconsciousness and irresponsible behaviour.<br> Also those do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> BPCD is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here is the answer:<br> '''1.''' An average basic internet user that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' Advanced computer users, governmental and public workers that need hardware and software features to prevent an intrusion and are skilled and aware enough so they can use all the built in hardware and software features and use additional encryption for official and personal data protection through secure productivity apps and tools.<br> '''3.''' Educational institutions that will teach online security, privacy and safety. Also that will make use of a device’s connections versatility as in hardware connectivity, as well as in software User Interface and User Expiriance utilising age adoptive “aperture Operating System” and featured secure online in-the-browser Workbench and added to it find the value in overall physical sturdiness and upgrade-ability.<br> TLDR; '''For the children age 9-99.'''<br> <strong>Ohh, yet another OLPC thingy I can see upcoming, or...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool to be used and abused by one and only - Microsoft at the end. Cudos to all people who made it and maintained it so long out of love for reaching out with otherwise good idea on educating children, but all of them not just patronising African nations, so.. no cigar.<br> We want to enable to use and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” corporations that will give away, rent or borrow Balthazars to those who are unable to afford it. (LEGO® Education, Google Education, various charities, foundations and EU initiatives, so we hope).<br> So Balthazar is <strong>NOT</strong> OLPC-alike, but it does follow some of OLPC product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is cool and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 3e32603d2f4398b39e2f2f6600fb6525135b2298 26 23 2019-08-27T13:50:46Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet.</strong> <strong>Secure, fast, inexpensive. Pick all three.</strong><br> BPCD - Balthazar Personal Computing Device is a 13.3" laptop based on RiscV processor(s) that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows CC, GNU-GPL, FOSS and EOMA guidelines.<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in at the most possible lowest price that should be available to everyone from an individual up to a large institutions.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> Google, Samsung, Acer, Dell and the other respective partners did indeed made inexpensive and lightweight laptops, but they are locked in a certain software and hardware ecosystems and actually offer not so many security features while appearing less flexible towards full FOSS, GNU-GPL and EOMA guidelines that we want to set as another standard. That ethical standard is not based on a profit, but on protecting and also educating population on how not to voluntary disseminate their data all over the interwebs, being used as a bait for large companies that take an advantage of such unconsciousness and irresponsible behaviour.<br> Also those do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> BPCD is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here is the answer:<br> '''1.''' An average basic internet user that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' Advanced computer users, governmental and public workers that need hardware and software features to prevent an intrusion and are skilled and aware enough so they can use all the built in hardware and software features and use additional encryption for official and personal data protection through secure productivity apps and tools.<br> '''3.''' Educational institutions that will teach online security, privacy and safety. Also that will make use of a device’s connections versatility as in hardware connectivity, as well as in software User Interface and User Expiriance utilising age adoptive “aperture Operating System” and featured secure online in-the-browser Workbench and added to it find the value in overall physical sturdiness and upgrade-ability.<br> TLDR; '''For the children age 9-99.'''<br> <strong>Ohh, yet another OLPC thingy I can see upcoming, or...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool to be used and abused by one and only - '''Microsoft''''''™''' at the end. Cudos to all people who made it and maintained it so long out of love for reaching out with otherwise good idea on educating children, but they missed that target to be worldwide and all of them, not just patronising African and other developing nations as they did at the beginning, so...no cigar.<br> We want to enable to use and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations that will buy '''Balthazars''' from us first and then give away, rent or borrow them to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', various charities, foundations and '''EU''' initiatives, so we hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of '''OLPC''' product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. bee73e00817df642e8d0fd67708eec03c5072eaf 27 26 2019-08-27T13:52:33Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>One laptop for the new internet.</strong> <strong>Secure, fast, inexpensive. Pick all three.</strong><br> BPCD - Balthazar Personal Computing Device is a 13.3" laptop based on RiscV processor(s) that contains all the hardware and software features and precautions to prevent any 3rd party intrusion into the system. While being versatile and robust it also strictly follows CC, GNU-GPL, FOSS and EOMA guidelines.<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where BPCD comes in at the most possible lowest price that should be available to everyone from an individual up to a large institutions.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> Google, Samsung, Acer, Dell and the other respective partners did indeed made inexpensive and lightweight laptops, but they are locked in a certain software and hardware ecosystems and actually offer not so many security features while appearing less flexible towards full FOSS, GNU-GPL and EOMA guidelines that we want to set as another standard. That ethical standard is not based on a profit, but on protecting and also educating population on how not to voluntary disseminate their data all over the interwebs, being used as a bait for large companies that take an advantage of such unconsciousness and irresponsible behaviour.<br> Also those do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> BPCD is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here is the answer:<br> '''1.''' An average basic internet user that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' Advanced computer users, governmental and public workers that need hardware and software features to prevent an intrusion and are skilled and aware enough so they can use all the built in hardware and software features and use additional encryption for official and personal data protection through secure productivity apps and tools.<br> '''3.''' Educational institutions that will teach online security, privacy and safety. Also that will make use of a device’s connections versatility as in hardware connectivity, as well as in software User Interface and User Expiriance utilising age adoptive “aperture Operating System” and featured secure online in-the-browser Workbench and added to it find the value in overall physical sturdiness and upgrade-ability.<br> TLDR; '''For the children age 9-99.'''<br> <strong>Ohh, yet another OLPC thingy I can see upcoming, or...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool to be used and abused by one and only - '''Microsoft™''' at the end. Cudos to all people who made it and maintained it so long out of love for reaching out with otherwise good idea on educating children, but they missed that target to be worldwide and all of them, not just patronising African and other developing nations as they did at the beginning, so...no cigar.<br> We want to enable to use and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations that will buy '''Balthazars''' from us first and then give away, rent or borrow them to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', various charities, foundations and '''EU''' initiatives, so we hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of '''OLPC''' product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 388077b9f2b33cf0fd97f3e579d7915b9a1d73b9 28 27 2019-08-27T16:08:53Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>'''<big>One laptop for the new internet.</big>'''</strong> <strong>Secure, fast, inexpensive and sustainable. Pick all three.</strong><br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' laptop based on '''RISC-V''' processor(s) that contains all the hardware and software features and precautions to prevent data-theft and any unwanted 3rd party intrusion into the system. While being versatile and robust it also strictly follows '''CC, GNU-GPL, FOSS''' and '''EOMA''' guidelines.<br> <small>What is all that FOSS and CC and ..?</small> → [[Glossary]]<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where '''BPCD''' comes in at the most possible lowest price that should be affordable to everyone - from an individual up to a large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> That ethical standard is not based on a profit, but on protecting and also educating population on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases personas to which such device just might appeal:<br> '''1.''' An average basic internet user that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' Advanced computer users, governmental and public workers that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' Educational institutions that will teach online security, privacy and safety. Also that will make use of a device’s connections versatility as in hardware connectivity, as well as in software User Interface and User Experience utilising age-adoptive “Aperture Operating System” and featured secure online in-the-browser Workbench and added to it to find the value in overall physical sturdiness and upgradeability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool to be used and abused by one and only - '''Microsoft™''' at the end. Cudos to all people who made it and maintained it so long and out of love for reaching out with otherwise good intention on educating children, but they missed to recognise that target is to be worldwide and all of them, not just patronising African and other developing nations, as they did at the beginning, so...no cigar.<br> We want to enable to use and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations that will buy '''Balthazars''' from us first and then give away, rent or borrow them to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', various charities, foundations and '''EU''' initiatives, so we hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of '''OLPC''' product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 431f70befba53f99347fe20c7451bed6c7198239 32 28 2019-08-27T16:37:58Z Harv 2 /* Balthazar - a Personal Computing Device */ wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>'''<big>One laptop for the new internet.</big>'''</strong> <strong>Secure, fast, inexpensive and sustainable. Pick all three.</strong><br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' laptop based on '''RISC-V''' processor(s) that contains all the hardware and software features and precautions to prevent data-theft and any unwanted 3rd party intrusion into the system. While being versatile and robust it also strictly follows '''CC, GNU-GPL, FOSS''' and '''EOMA''' guidelines.<br> <small>What is all that FOSS and CC and ..?</small> → [[Glossary]]<br> [[File:Ampere.jpg|thumb]]<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly propitiatory software that bounds a user to a manufacturer, this is where '''BPCD''' comes in at the most possible lowest price that should be affordable to everyone - from an individual up to a large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> That ethical standard is not based on a profit, but on protecting and also educating population on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases personas to which such device just might appeal:<br> '''1.''' An average basic internet user that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' Advanced computer users, governmental and public workers that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' Educational institutions that will teach online security, privacy and safety. Also that will make use of a device’s connections versatility as in hardware connectivity, as well as in software User Interface and User Experience utilising age-adoptive “Aperture Operating System” and featured secure online in-the-browser Workbench and added to it to find the value in overall physical sturdiness and upgradeability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool to be used and abused by one and only - '''Microsoft™''' at the end. Cudos to all people who made it and maintained it so long and out of love for reaching out with otherwise good intention on educating children, but they missed to recognise that target is to be worldwide and all of them, not just patronising African and other developing nations, as they did at the beginning, so...no cigar.<br> We want to enable to use and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations that will buy '''Balthazars''' from us first and then give away, rent or borrow them to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', various charities, foundations and '''EU''' initiatives, so we hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of '''OLPC''' product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 3919d50eef996a830655ddfa9b24b6b3f7ae2250 33 32 2019-08-27T19:47:14Z Admin 1 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>'''<big>One laptop for the new internet.</big>'''</strong> <strong>Secure, fast, inexpensive and sustainable. Pick all three.</strong><br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' laptop based on '''RISC-V''' processor(s) that contains all the hardware and software features and precautions to prevent data-theft and any unwanted 3rd party intrusion into the system. While being versatile and robust it also strictly follows '''CC, GNU-GPL, FOSS''' and '''EOMA''' guidelines.<br> <small>What is all that FOSS and CC and ..?</small> → [[Glossary]]<br> [[File:Ampere.jpg|thumb]]<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer, this is where '''BPCD''' comes in at the most possible lowest price that should be affordable to everyone - from an individual up to a large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> That ethical standard is not based on a profit, but on protecting and also educating population on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases personas to which such device just might appeal:<br> '''1.''' An average basic internet user that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' Advanced computer users, governmental and public workers that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' Educational institutions that will teach online security, privacy and safety. Also that will make use of a device’s connections versatility as in hardware connectivity, as well as in software User Interface and User Experience utilising age-adoptive “Aperture Operating System” and featured secure online in-the-browser Workbench and added to it to find the value in overall physical sturdiness and upgradeability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool to be used and abused by one and only - '''Microsoft™''' at the end. Cudos to all people who made it and maintained it so long and out of love for reaching out with otherwise good intention on educating children, but they missed to recognise that target is to be worldwide and all of them, not just patronising African and other developing nations, as they did at the beginning, so...no cigar.<br> We want to enable to use and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations that will buy '''Balthazars''' from us first and then give away, rent or borrow them to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', various charities, foundations and '''EU''' initiatives, so we hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of '''OLPC''' product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. f475e99770db7cfd2798d02488bebd9f7c533349 34 33 2019-08-28T09:34:41Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>'''<big>One laptop for the new internet.</big>'''</strong> <strong>Secure, fast, inexpensive and sustainable. Pick all three.</strong><br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' laptop based on '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''' card and in the near future '''RISC-V''' processor(s) that contains all the hardware and software features and precautions to prevent data-theft and any unwanted 3rd party intrusion into the system. While being versatile and robust it also strictly follows '''CC, GNU-GPL, FOSS''' and '''EOMA''' guidelines.<br> <small>What is all that FOSS and CC and ..?</small> → [[Glossary]]<br> [[File:Ampere.jpg|thumb]]<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer, this is where '''BPCD''' comes in at the most possible lowest price that should be affordable to everyone - from an individual up to a large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> That ethical standard is not based on a profit, but on protecting and also educating population on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases personas to which such device just might appeal:<br> '''1.''' An average basic internet user that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' Advanced computer users, governmental and public workers that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' Educational institutions that will teach online security, privacy and safety. Also that will make use of a device’s connections versatility as in hardware connectivity, as well as in software User Interface and User Experience utilising age-adoptive “Aperture Operating System” and featured secure online in-the-browser Workbench and added to it to find the value in overall physical sturdiness and upgradeability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool to be used and abused by one and only - '''Microsoft™''' at the end. Cudos to all people who made it and maintained it so long and out of love for reaching out with otherwise good intention on educating children, but they missed to recognise that target is to be worldwide and all of them, not just patronising African and other developing nations, as they did at the beginning, so...no cigar.<br> We want to enable to use and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations that will buy '''Balthazars''' from us first and then give away, rent or borrow them to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', various charities, foundations and '''EU''' initiatives, so we hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of '''OLPC''' product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. cdc5f75d865745063ccf0df6a27b6ac261b6ee6a 47 34 2019-09-03T01:49:34Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong><big>'''One laptop for the new internet.'''</big></strong> <strong>'''Secure, fast, inexpensive and sustainable. Pick all three.'''</strong><br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' laptop based on a few concepts from '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but strictly based on '''RISC-V''' processor(s) that contains all the hardware and software features and precautions to prevent data-theft and any unwanted 3rd party intrusion into the system. While being versatile and robust it also strictly follows '''GNU-GPL''', '''CC,''' FOSS''' and '''EOMA''' guidelines.<br> <small>What is all that FOSS and CC and ..?</small> → [[Glossary]]<br> [[File:Ampere.jpg|thumb]]<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer, this is where '''BPCD''' comes in at the most possible lowest price that should be affordable to everyone - from an individual up to a large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> That ethical standard is not based on a profit, but on protecting and also educating population on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3rd party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases personas to which such device just might appeal:<br> '''1.''' An average basic internet user that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' Advanced computer users, governmental and public workers that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' Educational institutions that will teach online security, privacy and safety. Also that will make use of a device’s connections versatility as in hardware connectivity, as well as in software User Interface and User Experience utilising age-adoptive “Aperture Operating System” and featured secure online in-the-browser Workbench and added to it to find the value in overall physical sturdiness and upgradeability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool to succumb to the various proprietary and commercial interests at the end of its life time. Kudos to all people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it missed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts worldwide, not just patronising African and other developing nations, so - no cigar.<br> We want to enable to use and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations that will get '''Balthazars''' from us, first and then give away, rent or borrow them to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', various charities, foundations and '''EU''' initiatives, so we hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of '''OLPC''' product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 36d61a528c0f38dc213703d247916c68842cab3a 48 47 2019-09-03T02:47:53Z Harv 2 /* Balthazar - a Personal Computing Device */ wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong><big>'''One laptop for the new internet.'''</big></strong><br> <strong>'''Secure, fast, inexpensive, upgradeable and sustainable. All of that.'''</strong><br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by '''RISC-V''' processor(s) that runs on <big>'''Linux OS'''</big>.<br> It contains all the hardware, software features and precautions to prevent data-theft and any unwanted 3<small>rd</small> party intrusion into the system.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and ..?</small> '''→''' [[Glossary]]<br> [[File:Ampere.jpg|thumb]]<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating population on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that is fully customizable. Added to it, educational community should find the value in overall physical sturdiness and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool to succumb to the various proprietary and commercial interests at the end of its life time. Kudos to all people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it missed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts worldwide, not just patronising African and other developing nations, so - no cigar.<br> We want to enable to use and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations that will get '''Balthazars''' from us, first and then give away, rent or borrow them to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', various charities, foundations and '''EU''' initiatives, so we hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of '''OLPC''' product design innovations and features, adopted and improved for today’s performance requirements focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover additional connectors and IO’s  also enable them to tinker and create their own devices or program LEGO sensors and actuators while retractable GPIO module, enables them in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every other manufacturer. (Matrix, VeX, Arduino etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. db9f54c5f3cb361282c05fe41b7a9597408a7ee5 52 48 2019-09-03T04:12:47Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong><big>'''One laptop for the new internet.'''</big></strong><br> <strong>'''Secure, fast, inexpensive, upgradeable and sustainable. All of that.'''</strong><br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by '''RISC-V''' processor(s) open architecture that runs on <big>'''Linux OS'''</big>.<br> It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Ampere.jpg|thumb]]<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps.<br> Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time.<br> Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar.<br> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO©''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO©''', '''Matrix''', '''VeX''', '''Arduino''' etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 1af13ae446555623a9843ed91a09beb7cb8d963a 53 52 2019-09-03T04:15:31Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong><big>'''One laptop for the new internet.'''</big></strong><br> <strong>'''Secure, fast, inexpensive, upgradeable and sustainable. All of that.'''</strong><br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by '''RISC-V''' processor(s) open architecture that runs on <big>'''Linux OS'''</big>.<br> It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Ampere.jpg|thumb]]<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps.<br> Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time.<br> Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar.<br> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. b4dac0d29e7f89afeca6442433f4b82a1e4252f9 4 3 8 2019-08-27T10:41:12Z Harv 2 Created page with "Balthazar is an international consortium that sets in motion and leads a new approach in the design and the construction of a full EOMA and GNU-GPL compliant FOSS laptop as a..." wikitext text/x-wiki Balthazar is an international consortium that sets in motion and leads a new approach in the design and the construction of a full EOMA and GNU-GPL compliant FOSS laptop as a personal computing device. PCD will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. Consortium consists of an industry and academia personas. Certain percentage of the profit will go directly to FOSS software developers to create secure, easy to use and intuitive user-friendly software and apps for the Balthazar Personal Computing Device. 56c49165a80165beede836ace483b667f6ff1d01 4 4 9 2019-08-27T10:43:26Z Harv 2 Created page with "Everything Balthazar does is FOSS and GPL v2, GPL v3 and copyleft with a CC-by-SA 4.0 where licenses apply, except partners’ copyrights and trademarks." wikitext text/x-wiki Everything Balthazar does is FOSS and GPL v2, GPL v3 and copyleft with a CC-by-SA 4.0 where licenses apply, except partners’ copyrights and trademarks. 20ea010045b5229743f2863fa15ea2a16b7c05b2 10 9 2019-08-27T10:44:26Z Harv 2 wikitext text/x-wiki Everything Balthazar does is FOSS and GPL v2, GPL v3 and copyleft with a CC-by-SA 4.0 where licenses apply, except partners’ respective copyrights and trademarks. e1dae2cb4e84a8fa74b63cb2c4361224ff12d0cb 24 10 2019-08-27T13:26:34Z Harv 2 wikitext text/x-wiki Everything Balthazar does is FOSS and GPL v2, GPL v3 and copyleft with a CC-by-SA 4.0 where licenses apply, except partners’ respective copyrights and trademarks. Otherwise - you are on your own here. 570971d4edc684d64b25286c12188debb3db82dd 25 24 2019-08-27T13:27:12Z Harv 2 wikitext text/x-wiki Everything Balthazar does is FOSS and GPL v2, GPL v3 and copyleft with a CC-by-SA 4.0 where licenses apply, except partners’ respective copyrights and trademarks. Otherwise - you are on your own around here. 7ec6d46fe07572a70c6c78ebe2fab9a6a51d45a9 0 5 12 2019-08-27T12:02:27Z Harv 2 Created page with "'''Basic specifications and features'''<br> It is made for Trisquel GNU, Debian and Ubuntu.<br> 1. Fanless - (less movable parts means more battery time for the processing..." wikitext text/x-wiki '''Basic specifications and features'''<br> It is made for Trisquel GNU, Debian and Ubuntu.<br> 1. Fanless - (less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components.)<br>   2. Superfast boot time (nobody and especially children has/have the time to wait)<br> Ever since C64/AMIGA times computers should be able to be switched on/off.<br> Also it is booting using libreboot/coreboot.<br> 3. It has upgrade-able RAM and a processor board featuring second SoC/SoM attachment port.<br> 4. A non-glare screen size is 13.3” 16:10 full HD resolution (200 dpi +) and provides far less strain on user's eyes.<br> 5. A non-reflective (button driven backlight “off”) monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> 6. LED backlit color mode, with an alternance of red, green and blue pixels.<br> 7. A non-glare touch PCAP screen (Projected CAPacitive) as an optional addition for those who like to have fingers on the screen.<br> 8. A detachable webcam with a slide lens cover and a hardware switch for on/off<br> 9. A real volume ceramic wheel potentiometer with a “click” for the on/off functionality.<br>   10. LEGO® Power Functions connector for powering and control actuators, also Power Functions can be used to recharge battery using LEGO® or alike photovoltaic sets. <br>   11. RJ-12 LEGO® “shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> 12. Covered, retractable and flexible ribbon attached PIN array - GPIO (as is in RaspberryPi) General Purpose Input Output for connecting all the things you want to connect.<br> 13. Quick charging battery - Long Life Cycle Polymer 10000 mAh – recyclable.<br> 14. Small hot-swap enabling battery.<br> 15. Modular on-board power supply ( follows full ACPI spec.)<br> 16. Waterproof keyboard with ThinkPad style track point.<br> 17. A 3 segments flat-flush touch pad in a “Wacom” style with mode for the extended touch-pad draw and gestures.<br> It has 5 hardware switches for: the camera, speakers, the microphone array, WI-Fi and ethernet card. It comes with a detachable USB gender-changer dongle - that should prevent anyone to plug in USB stick unless is password unlocked, also when taken out prevents anyone to stick USB-anything in. A casing is a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added studs.<br> Optional:<br> A stylus for touch-pad drawing (enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.)<br> LEGO® keychain for the USB dongle.<br>   c84960b9bf793b58a521bb63960006cf11780f14 13 12 2019-08-27T12:16:12Z Harv 2 wikitext text/x-wiki '''Basic specifications and features'''<br> It is made for Trisquel GNU, Debian and Ubuntu.<br> '''1.''' Fanless - (less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components.)<br>   '''2.''' Superfast boot time (nobody and especially children has/have the time to wait.)Ever since C64/AMIGA times computers should be also able to be switched on/off fast.<br> Also it is booting using libreboot/coreboot.<br> '''3.''' It has upgrade-able RAM and a processor board featuring second SoC/SoM attachment port.<br> '''4.''' A non-glare screen size is 13.3” 16:10 full HD resolution (200 dpi +) and provides far less strain on user's eyes.<br> '''5.''' A non-reflective (button driven backlight “off”) monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''6.''' LED backlit color mode, with an alternance of red, green and blue pixels.<br> '''7.''' A non-glare touch PCAP screen (Projected CAPacitive) as an optional addition for those who like to have fingers on the screen.<br> '''8.''' A detachable webcam with a slide lens cover and a hardware switch for on/off<br> '''9.''' A real volume ceramic wheel potentiometer with a “click” for the on/off functionality.<br>   '''10.''' LEGO® Power Functions connector for powering and control actuators, also Power Functions can be used to recharge battery using LEGO® or alike photovoltaic sets. <br>   '''11.''' RJ-12 LEGO® “shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> '''12.''' Covered, retractable and flexible ribbon attached PIN array - GPIO (as is in RaspberryPi) General Purpose Input Output for connecting all the things you want to connect.<br> '''13.''' Quick charging battery - Long Life Cycle Polymer 10000 mAh – recyclable.<br> '''14.''' Small hot-swap enabling battery.<br> '''15.''' Modular on-board power supply ( follows full ACPI spec.)<br> '''16.''' Waterproof keyboard with ThinkPad style track point.<br> '''17.''' A 3 segments flat-flush touch pad in a “Wacom” style with mode for the extended touch-pad draw and gestures.<br> It has 5 hardware switches for: the camera, speakers, the microphone array, WI-Fi and ethernet card. It comes with a detachable USB gender-changer dongle - that should prevent anyone to plug in USB stick unless is password unlocked, also when taken out prevents anyone to stick USB-anything in. A casing is a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added studs.<br> '''Optional:'''<br> A stylus for touch-pad drawing (enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.)<br> LEGO® keychain for the USB dongle.<br>   4bb466c02e80c6644150dffc878bd8eb01d74ffb 14 13 2019-08-27T12:19:55Z Harv 2 wikitext text/x-wiki '''Basic specifications and features'''<br> It is made for Trisquel GNU, Debian and Ubuntu.<br> '''1.''' Fanless - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components.<br>   '''2.''' Superfast boot time as nobody and especially children has/have the time to wait.<br> Ever since C64/AMIGA times computers should be also able to be switched on/off fast.<br> Also it is booting using libreboot/coreboot.<br> '''3.''' It has upgrade-able RAM and a processor board featuring second SoC/SoM attachment port.<br> '''4.''' A non-glare screen size is 13.3” 16:10 full HD resolution (200 dpi +) and provides far less strain on user's eyes.<br> '''5.''' A non-reflective (button driven backlight “off”) monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''6.''' LED backlit color mode, with an alternance of red, green and blue pixels.<br> '''7.''' A non-glare touch PCAP screen (Projected CAPacitive) as an optional addition for those who like to have fingers on the screen.<br> '''8.''' A detachable webcam with a slide lens cover and a hardware switch for on/off<br> '''9.''' A real volume ceramic wheel potentiometer with a “click” for the on/off functionality.<br>   '''10.''' LEGO® Power Functions connector for powering and control actuators, also Power Functions can be used to recharge battery using LEGO® or alike photovoltaic sets. <br>   '''11.''' RJ-12 LEGO® “shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> '''12.''' Covered, retractable and flexible ribbon attached PIN array - GPIO - General Purpose Input Output for connecting all the things you want to connect it to.<br> '''13.''' Quick charging battery - Long Life Cycle Polymer 10000 mAh – recyclable.<br> '''14.''' Small hot-swap enabling battery.<br> '''15.''' Modular on-board power supply ( follows full ACPI spec.)<br> '''16.''' Waterproof keyboard with ThinkPad style track point.<br> '''17.''' A 3 segments flat-flush touch pad in a “Wacom” style with mode for the extended touch-pad draw and gestures.<br> It has 5 hardware switches for: the camera, speakers, the microphone array, WI-Fi and ethernet card. It comes with a detachable USB gender-changer dongle - that should prevent anyone to plug in USB stick unless is password unlocked, also when taken out prevents anyone to stick USB-anything in. A casing is a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added studs.<br> '''Optional:'''<br> A stylus for touch-pad drawing (enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.)<br> LEGO® keychain for the USB dongle.<br> [[Want to know more?]]   bfec5a9e6255fcbce78687292eb8f2b91c1fb50d 19 14 2019-08-27T12:40:01Z Harv 2 wikitext text/x-wiki '''Basic specifications and features'''<br> It is made for Trisquel GNU, Debian and Ubuntu.<br> '''1.''' Fanless - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components.<br>   '''2.''' Superfast boot time as nobody and especially children has/have the time to wait.<br> Ever since C64/AMIGA times computers should be also able to be switched on/off fast.<br> Also it is booting using libreboot/coreboot BIOS.<br> '''3.''' It has upgrade-able RAM and a processor board featuring second SoC/SoM attachment port.<br> '''4.''' A non-glare screen size is 13.3” 16:10 full HD resolution (200 dpi +) and provides far less strain on user's eyes.<br> '''5.''' A non-reflective (button driven backlight “off”) monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''6.''' LED backlit color mode, with an alternance of red, green and blue pixels.<br> '''7.''' A non-glare touch PCAP screen (Projected CAPacitive) as an optional addition for those who like to have fingers on the screen.<br> '''8.''' A detachable webcam with a slide lens cover and a hardware switch for on/off<br> '''9.''' A real volume ceramic wheel potentiometer with a “click” for the on/off functionality.<br>   '''10.''' LEGO® Power Functions connector for powering and control actuators, also Power Functions can be used to recharge battery using LEGO® or alike photovoltaic sets. <br>   '''11.''' RJ-12 LEGO® “shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> '''12.''' Covered, retractable and flexible ribbon attached PIN array - GPIO - General Purpose Input Output for connecting all the things you want to connect it to.<br> '''13.''' Quick charging battery - Long Life Cycle Polymer 10000 mAh – recyclable.<br> '''14.''' Small hot-swap enabling battery.<br> '''15.''' Modular on-board power supply ( follows full ACPI spec.)<br> '''16.''' Waterproof keyboard with ThinkPad style track point.<br> '''17.''' A 3 segments flat-flush touch pad in a “Wacom” style with mode for the extended touch-pad draw and gestures.<br> It has 5 hardware switches for: the camera, speakers, the microphone array, WI-Fi and ethernet card. It comes with a detachable USB gender-changer dongle - that should prevent anyone to plug in USB stick unless is password unlocked, also when taken out prevents anyone to stick USB-anything in. A casing is a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added studs.<br> '''Optional:'''<br> A stylus for touch-pad drawing (enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.)<br> LEGO® keychain for the USB dongle.<br> [[Want to know more?]]   539da6e82d2dfeaea4a678f8ce4af4e0547b8559 36 19 2019-08-28T09:38:16Z Harv 2 wikitext text/x-wiki '''Basic specifications and features'''<br> It is made for Trisquel GNU, Debian and Ubuntu.<br> '''1.''' Fanless - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components.<br>   '''2.''' Superfast boot time as nobody and especially children has/have the time to wait.<br> Ever since C64/AMIGA times computers should be also able to be switched on/off fast.<br> Also it is booting using libreboot/coreboot BIOS.<br> It suspends properly to RAM and goes to hibernate when battery is at 20%. Properly.<br> '''3.''' It has upgradeable RAM and a processor board featuring second SoC/SoM attachment port.<br> '''4.''' A non-glare screen size is 13.3” 16:10 full HD resolution (200 dpi +) and provides far less strain on user's eyes.<br> '''5.''' A non-reflective (button driven backlight “off”) monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''6.''' LED backlit color mode, with an alternance of red, green and blue pixels.<br> '''7.''' A non-glare touch PCAP screen (Projected CAPacitive) as an optional addition for those who like to have fingers on the screen.<br> '''8.''' A detachable webcam with a slide lens cover and a hardware switch for on/off<br> '''9.''' A real volume ceramic wheel potentiometer with a “click” for the on/off functionality.<br>   '''10.''' LEGO® Power Functions connector for powering and control actuators, also Power Functions can be used to recharge battery using LEGO® or alike photovoltaic sets. <br>   '''11.''' RJ-12 LEGO® “shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> '''12.''' Covered, retractable and flexible ribbon attached PIN array - GPIO - General Purpose Input Output for connecting all the things you want to connect it to.<br> '''13.''' Quick charging battery - Long Life Cycle Polymer 10000 mAh – recyclable.<br> '''14.''' Small hot-swap enabling battery.<br> '''15.''' Modular on-board power supply ( follows full ACPI spec.)<br> '''16.''' Waterproof keyboard with ThinkPad style track point.<br> '''17.''' A 3 segments flat-flush touch pad in a “Wacom” style with mode for the extended touch-pad draw and gestures.<br> It has 5 hardware switches for: the camera, speakers, the microphone array, WI-Fi and ethernet card. It comes with a detachable USB gender-changer dongle - that should prevent anyone to plug in USB stick unless is password unlocked, also when taken out prevents anyone to stick USB-anything in. A casing is a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added studs.<br> '''Optional:'''<br> A stylus for touch-pad drawing (enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.)<br> LEGO® keychain for the USB dongle.<br> [[Want to know more?]]   fea83c34d23d7a6e8256f24175d859d65c63e089 37 36 2019-08-28T10:00:32Z Harv 2 wikitext text/x-wiki '''Basic specifications and features'''<br> It is made for Trisquel GNU, Debian and Ubuntu 64 bit for ARM.<br> '''1.''' Fanless - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components.<br>   '''2.''' Boot and sleep. Superfast boot time as nobody and especially children has/have the time to wait.<br> Ever since C64/AMIGA times computers should be also able to be switched on/off fast.<br> Also it is booting using libreboot/coreboot BIOS.<br> It suspends to RAM and goes to hibernate when battery is at 20%. Properly.<br> '''3.''' It has upgradeable RAM and a processor board featuring second SoC/SoM attachment port.<br> '''4.''' A non-glare screen size is 13.3” 16:10 full HD resolution (200 dpi +) and provides far less strain on user's eyes.<br> '''5.''' A non-reflective (button driven backlight “off”) monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''6.''' LED backlit color mode, with an alternance of red, green and blue pixels.<br> '''7.''' A non-glare touch PCAP screen (Projected CAPacitive) as an optional addition for those who like to have fingers on the screen.<br> '''8.''' A detachable webcam with a slide lens cover and a hardware switch for on/off<br> '''9.''' A real volume ceramic wheel potentiometer with a “click” for the on/off functionality.<br>   '''10.''' LEGO® Power Functions connector for powering and control actuators, also Power Functions can be used to recharge battery using LEGO® or alike photovoltaic sets. <br>   '''11.''' RJ-12 LEGO® “shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> '''12.''' Covered, retractable and flexible ribbon attached PIN array - GPIO - General Purpose Input Output for connecting all the things you want to connect it to.<br> '''13.''' Quick charging battery - Long Life Cycle Polymer 10000 mAh – recyclable.<br> '''14.''' Small hot-swap enabling battery.<br> '''15.''' Modular on-board power supply ( follows full ACPI spec.)<br> '''16.''' Waterproof keyboard with ThinkPad style track point.<br> '''17.''' A 3-segments flat-flush touch pad in a “Wacom” style with a mode for the extended touch-pad draw and gestures.<br> '''Other features:''' It has 5 hardware switches for:<br> the camera, speakers, the microphones array, Wi-Fi and Ethernet card.<br> It comes with a detachable USB gender-changer dongle - that should prevent anyone to plug in USB-anything unless it is password unlocked, also when taken out prevents anyone to stick USB-anything in.<br> A casing is a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added studs.<br> '''Optional:'''<br> A stylus for touch-pad drawing (enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.)<br> LEGO® keychain for the USB dongle.<br> [[Want to know more?]]   3f85dd78c320169c7a8ac1d99c4951160f9976ee 38 37 2019-08-28T10:53:16Z Harv 2 wikitext text/x-wiki '''Basic specifications and features'''<br> It is made for Trisquel GNU, Debian and Ubuntu 64 bit for ARM.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components.<br>   '''Boot and sleep''' - fast boot time as nobody and especially children has/have the time to wait.<br> Ever since C64/AMIGA times computers should be also able to be switched on/off fast, so using libreboot/coreboot BIOS should do it.<br> It suspends to RAM and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring second SoC/SoM attachment port or a slot.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) and provides far less strain on user's eyes.<br> '''A non-reflective''' - button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' ceramic potentiometer with a “click” for the on/off functionality.<br>   '''LEGO® Power Functions''' - a connector for powering and the control of actuators. Power Functions connector can be used to recharge a battery using LEGO® or alike photovoltaic sets with Power Functions adapter.<br>   '''RJ-12 LEGO®''' “shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> '''GPIO''' - a covered, retractable and flexible ribbon attached PIN array General Purpose Input Output for connecting all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' on-board power supply that follows full ACPI specification.<br> '''Waterproof keyboard''' - with ThinkPad alike track point.<br> '''Multitouch pad''' - flat-flush positioned above the keyboard. It has a “Wacom” mode for the extended stylus or a finger draw and is multi finger gestures aware.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''Security and privacy features:'''<br> '''Five (5) hardware off/on switches'''- webcam (detachable), speakers, the microphones array (detachable), Wi-Fi and Ethernet card.<br> '''Detachable USB gender-changer dongle''' that prevents anyone to plug in USB-anything unless it is attached and a password unlocked, also when taken out prevents anyone to stick USB-anything in.<br> '''A few extras:'''<br> '''TEMPEST-shield''' - shields from any external and internal electromagnetic radiation. Lead-free but not inexpensive, mind you.<br> '''A stylus''' - for multitouch-pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more?]]   b862c4da00eeda9ab70319d77848fa071b544a5a 39 38 2019-08-28T11:01:36Z Harv 2 wikitext text/x-wiki '''Basic specifications and features'''<br> It is made to run Trisquel GNU, Debian and Ubuntu variants of 64 bit low latency kernel for ARM.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components.<br>   '''Boot and sleep''' - fast boot time as nobody and especially children has/have the time to wait.<br> Ever since C64/AMIGA times computers should be also able to be switched on/off fast, so using libreboot/coreboot BIOS should do it.<br> It suspends to RAM and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring second SoC/SoM attachment port or a slot.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) and provides far less strain on user's eyes.<br> '''A non-reflective''' - button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br>   '''LEGO® Power Functions''' - a connector for powering and the control of actuators. Power Functions connector can be used to recharge a battery using LEGO® or alike photovoltaic sets with Power Functions adapter.<br>   '''RJ-12 LEGO®''' - “a shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> '''GPIO''' - a covered, retractable and a flexible flat-ribbon cable connecting General Purpose Input Output PIN array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full ACPI specification.<br> '''Waterproof keyboard''' - with ThinkPad alike track point.<br> '''Multitouch pad''' - flat-flush positioned above the keyboard. It has a “Wacom” mode for the extended stylus or a finger draw and is multi finger gestures aware.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''Security and privacy features:'''<br> '''Five (5) hardware off/on switches'''- webcam (detachable), speakers, the microphones array (detachable), Wi-Fi and Ethernet card.<br> '''Detachable USB gender-changer dongle''' - that prevents anyone to plug in USB-anything unless it is attached and a password unlocked, also when taken out prevents anyone to stick USB-anything in.<br> '''A few extras:'''<br> '''TEMPEST-shield''' - shields from any external and internal electromagnetic radiation. Lead-free but not inexpensive, mind you.<br> '''A stylus''' - for multitouch-pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more?]]   6cf2e28a5fa1231271400e2b9adfc581b7778a01 40 39 2019-08-28T11:16:21Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' low-latency kernel for '''ARM'''.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components. Think quiet.<br>   '''Boot and sleep''' - fast boot time as nobody and especially children has/have the time to wait. Ever since C64/AMIGA times computers should be also able to be switched on/off fast, so using libreboot/coreboot BIOS should do it.<br> It suspends to RAM and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring second SoC/SoM attachment port or a slot.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) and provides far less strain on user's eyes.<br> '''A non-reflective''' - button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br>   '''LEGO® Power Functions''' - a connector for powering and the control of actuators. '''Power Functions''' connector can be used to recharge a battery using '''LEGO®''' or similar photovoltaic sets with extra '''Power Functions''' adapter.<br>   '''RJ-12 LEGO®''' - “a shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> '''GPIO''' - a covered, retractable and a flexible flat-ribbon cable connecting General Purpose Input Output PIN array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full ACPI specification.<br> '''Waterproof keyboard''' - with ThinkPad alike track point.<br> '''Multitouch pad''' - flat-flush positioned above the keyboard. It has a “Wacom” mode for the extended stylus or a finger draw and is multi finger gestures aware.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Security and privacy features:</big>'''<br> '''Five (5) hardware off/on switches'''- webcam (detachable), speakers, the microphones array (detachable), Wi-Fi and Ethernet card.<br> '''Detachable USB gender-changer dongle''' - that prevents anyone to plug in USB-anything unless it is attached and a password unlocked, also when taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield''' - shields from any external and internal electromagnetic radiation. Lead-free but not inexpensive, mind you.<br> '''A stylus''' - for multitouch-pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''LEGO® Power Functions''' adapter - for connecting external photovoltaic chargers<br> '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more?]]   5a97613a5c7dc10deffadc4ffb3a0d2b7be2563c 4 7 17 2019-08-27T12:34:30Z Harv 2 Created page with "'''We guarantee safe, secure and private browsing of our pages.'''<br> We will not use in '''ANY CASE ANY OF YOUR DATA''' even if you submit some.<br>" wikitext text/x-wiki '''We guarantee safe, secure and private browsing of our pages.'''<br> We will not use in '''ANY CASE ANY OF YOUR DATA''' even if you submit some.<br> bcf55554331ffd9b7cc0308529e0cbf526fd2165 4 8 18 2019-08-27T12:39:14Z Harv 2 Created page with "Everything we do is FOSS and GPL v2, GPL v3 and copyleft with a CC-by-SA 4.0 where licenses apply, except partners’ copyrights and trademarks. They might go after you if the..." wikitext text/x-wiki Everything we do is FOSS and GPL v2, GPL v3 and copyleft with a CC-by-SA 4.0 where licenses apply, except partners’ copyrights and trademarks. They might go after you if they see that fit. We won't. 2440f68de1f757282316e102ce5e77e582a772aa 0 9 29 2019-08-27T16:16:26Z Harv 2 Created page with "<big>GLOSSARY:</big>  '''OS''' - Operating System<br> '''FOSS''' - Free and Open Source Software<br> '''OLPC''' - One laptop Per Child<br> '''SW''' - Software<br> '''HW'..." wikitext text/x-wiki <big>GLOSSARY:</big>  '''OS''' - Operating System<br> '''FOSS''' - Free and Open Source Software<br> '''OLPC''' - One laptop Per Child<br> '''SW''' - Software<br> '''HW''' - Hardware<br> '''GNU - GPL'''  - GNU is Not Unix, General Public Licence<br> '''CC''' - Creative Commons<br> '''CC-BY-SA''' - Creative Commons Attribution–ShareAlike License<br> '''FSL''' - A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software.<br> '''ETQ''' - Excellence Through Quality<br> '''PCD''' - Personal computing Device, a laptop, but not quite.<br>  '''EOMA''' - Embedded Open Modular Architecture<br> dec02a7a178c2dd35be734386025f6764eed2bfc 30 29 2019-08-27T16:27:12Z Harv 2 wikitext text/x-wiki <big>'''GLOSSARY:'''</big>  '''OS''' - Operating System<br> '''FOSS''' - Free and Open Source Software<br> '''OLPC''' - One laptop Per Child<br> '''SW''' - Software<br> '''HW''' - Hardware<br> '''GNU - GPL'''  - GNU is Not Unix, General Public Licence<br> '''CC''' - Creative Commons<br> '''CC-BY-SA''' - Creative Commons Attribution–ShareAlike License<br> '''FSL''' - A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software.<br> '''ETQ''' - Excellence Through Quality<br> '''PCD''' - Personal Computing Device, a laptop, but not quite.<br> '''EOMA''' - Embedded Open Modular Architecture<br> '''RISC-V''' - The Free and Open RISC Instruction Set Architecture RISC-V is a free and open ISA enabling a new era of processor innovation through open standard collaboration.<br> RISC-V ISA delivers a new level of free, extensible software and hardware freedom on architecture, paving the way for the next 50 years of computing design and innovation.<br> '''RISC''' - Reduced Instruction Set Computer 96badec4f5f360588e1bb3bb0b783828b3a52f42 35 30 2019-08-28T09:35:36Z Harv 2 wikitext text/x-wiki <big>'''GLOSSARY:'''</big>  '''OS''' - Operating System<br> '''FOSS''' - Free and Open Source Software<br> '''OLPC''' - One Laptop Per Child<br> '''SW''' - Software<br> '''HW''' - Hardware<br> '''GNU - GPL'''  - GNU is Not Unix, General Public Licence<br> '''CC''' - Creative Commons<br> '''CC-BY-SA''' - Creative Commons Attribution–ShareAlike License<br> '''FSL''' - A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software.<br> '''ETQ''' - Excellence Through Quality<br> '''PCD''' - Personal Computing Device, a laptop, but not quite.<br> '''EOMA''' - Embedded Open Modular Architecture<br> '''RISC-V''' - The Free and Open RISC Instruction Set Architecture RISC-V is a free and open ISA enabling a new era of processor innovation through open standard collaboration.<br> RISC-V ISA delivers a new level of free, extensible software and hardware freedom on architecture, paving the way for the next 50 years of computing design and innovation.<br> '''RISC''' - Reduced Instruction Set Computer 839d09f8abc51de38951fa458735fd449333be02 54 35 2019-09-03T04:31:50Z Harv 2 wikitext text/x-wiki <big>'''GLOSSARY:'''</big>  '''OS''' - Operating System '''SW''' - Software<br> '''HW''' - Hardware<br> '''PCD''' - Personal Computing Device, a laptop.<br> '''FSL''' - A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software.<br> '''FOSS''' - Free and Open Source Software<br> '''GNU - GPL'''  - GNU is Not Unix, General Public Licence<br> '''EOMA''' - Embedded Open Modular Architecture<br> '''RISC-V''' - '''The Free and Open RISC Instruction Set Architecture''' '''RISC-V''' is a free and open '''ISA''' enabling a new era of processor innovation through open standard collaboration.<br> '''RISC-V ISA''' delivers a new level of free, extensible software and hardware freedom on architecture, paving the way for the next 50 years of computing design and innovation.<br> '''ISA''' - Instruction Set Architecture<br> '''RISC''' - Reduced Instruction Set Computer<br> '''GPIO''' - General Purpose Input Output<br> '''CC''' - Creative Commons<br> '''CC-BY-SA''' - Creative Commons Attribution–ShareAlike License<br> '''ETQ''' - Excellence Through Quality<br> '''OLPC''' - One Laptop Per Child 771be1cd1bd2bd6032d201b543d1cbd329d8d118 55 54 2019-09-03T04:33:47Z Harv 2 wikitext text/x-wiki '''OS''' - Operating System '''SW''' - Software<br> '''HW''' - Hardware<br> '''PCD''' - Personal Computing Device, a laptop.<br> '''FSL''' - A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software.<br> '''FOSS''' - Free and Open Source Software<br> '''GNU - GPL'''  - GNU is Not Unix, General Public Licence<br> '''EOMA''' - Embedded Open Modular Architecture<br> '''RISC-V''' - '''The Free and Open RISC Instruction Set Architecture''' '''RISC-V''' is a free and open '''ISA''' enabling a new era of processor innovation through open standard collaboration.<br> '''RISC-V ISA''' delivers a new level of free, extensible software and hardware freedom on architecture, paving the way for the next 50 years of computing design and innovation.<br> '''ISA''' - Instruction Set Architecture<br> '''RISC''' - Reduced Instruction Set Computer<br> '''GPIO''' - General Purpose Input Output<br> '''CC''' - Creative Commons<br> '''CC-BY-SA''' - Creative Commons Attribution–ShareAlike License<br> '''ETQ''' - Excellence Through Quality<br> '''OLPC''' - One Laptop Per Child eee935bd02d6f6c49c9a337b2a0e4c1f9e8ff7e3 56 55 2019-09-03T04:37:19Z Harv 2 wikitext text/x-wiki '''‽''' '''OS''' - Operating System<br> '''SW''' - Software<br> '''HW''' - Hardware<br> '''PCD''' - Personal Computing Device, a laptop, but with added extras.<br> '''FSL''' - A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software.<br> '''FOSS''' - Free and Open Source Software<br> '''GNU - GPL'''  - GNU is Not Unix, General Public Licence<br> '''EOMA''' - Embedded Open Modular Architecture<br> '''RISC-V''' - '''The Free and Open RISC Instruction Set Architecture''' '''RISC-V''' is a free and open '''ISA''' enabling a new era of processor innovation through open standard collaboration.<br> '''RISC-V ISA''' delivers a new level of free, extensible software and hardware freedom on architecture, paving the way for the next 50 years of computing design and innovation.<br> '''ISA''' - Instruction Set Architecture<br> '''RISC''' - Reduced Instruction Set Computer<br> '''GPIO''' - General Purpose Input Output<br> '''CC''' - Creative Commons<br> '''CC-BY-SA''' - Creative Commons Attribution–ShareAlike License<br> '''ETQ''' - Excellence Through Quality<br> '''OLPC''' - One Laptop Per Child c76842047ec16cbbfc747a7d352c516cc01d95e0 6 10 31 2019-08-27T16:36:37Z Harv 2 wikitext text/x-wiki A place holder for real Balthazar 4603a45b24399fa62b64c7ea9ca2aa227063f997 4 12 44 2019-09-02T18:08:21Z Admin 1 Created page with "* Remove unnecessary stuff from side menu. * Mobile CSS * Color schema" wikitext text/x-wiki * Remove unnecessary stuff from side menu. * Mobile CSS * Color schema c2abbf7589f440f4349a8fad7300a9021d6fff85 45 44 2019-09-02T18:10:45Z Admin 1 wikitext text/x-wiki * Remove unnecessary stuff from side menu. * Mobile CSS * Color schema * Footer 7c712fe256e059227532c5518c9cd60f26d68b13 46 45 2019-09-02T18:11:52Z Admin 1 wikitext text/x-wiki * Menu bar * Remove unnecessary stuff from side menu. * Mobile CSS * Color schema * Footer fc80d30bbfa0ea0eaecbb8e7bab350157f2473d9 0 13 49 2019-09-03T03:21:15Z Harv 2 Created page with "here comes UI guidelines for schools, edu and basic user." wikitext text/x-wiki here comes UI guidelines for schools, edu and basic user. 6317f329851fba083dbf9c96fc6cbec307d16606 0 14 50 2019-09-03T03:22:12Z Harv 2 Created page with "here comes overall UX with a special accent on edu." wikitext text/x-wiki here comes overall UX with a special accent on edu. 034ddd41eae9b5bed1a9e29ad4f7f643e786acbb 0 15 51 2019-09-03T03:24:17Z Harv 2 Created page with "here comes a concept and a guidelines for AOS..(is it just addressing settings in a window environment or a real custom made OS? I do not know yet..)" wikitext text/x-wiki here comes a concept and a guidelines for AOS..(is it just addressing settings in a window environment or a real custom made OS? I do not know yet..) f3f0bb02f0e502fa41934c9d3fc6d574e34bea13 0 9 57 56 2019-09-03T04:38:57Z Harv 2 wikitext text/x-wiki '''OS''' - Operating System<br> '''SW''' - Software<br> '''HW''' - Hardware<br> '''PCD''' - Personal Computing Device, a laptop, but with added extras.<br> '''FSL''' - A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software.<br> '''FOSS''' - Free and Open Source Software<br> '''GNU - GPL'''  - GNU is Not Unix, General Public Licence<br> '''EOMA''' - Embedded Open Modular Architecture<br> '''RISC-V''' - '''The Free and Open RISC Instruction Set Architecture''' '''RISC-V''' is a free and open '''ISA''' enabling a new era of processor innovation through open standard collaboration.<br> '''RISC-V ISA''' delivers a new level of free, extensible software and hardware freedom on architecture, paving the way for the next 50 years of computing design and innovation.<br> '''ISA''' - Instruction Set Architecture<br> '''RISC''' - Reduced Instruction Set Computer<br> '''GPIO''' - General Purpose Input Output<br> '''CC''' - Creative Commons<br> '''CC-BY-SA''' - Creative Commons Attribution–ShareAlike License<br> '''ETQ''' - Excellence Through Quality<br> '''OLPC''' - One Laptop Per Child 07c96b44d1d902ef747d2fb5f0b4a249945ac2bc 100 57 2019-09-05T05:17:48Z Harv 2 wikitext text/x-wiki '''OS''' - Operating System<br> '''SW''' - Software<br> '''HW''' - Hardware<br> '''CPU''' - Central Processing Unit. A very small pile of interconnected transistors that go off or on and process the incoming instructions requests.<br> '''RAM''' - Random Access Memory. It can be written to, read from and erased too.<br> Bigger it is, better it is for the '''CPU''' and '''OS'''. And user.<br> '''ROM''' - Read Only Memory. It can not be written to by user or '''OS'''. Usually contains an instruction set.<br> '''BIOS''' - Basic Input Output System. When device is powered on it checks its physical integrity and various settings before it boots into '''OS'''.<br> It can be flushed and updated for better performance and additional '''HW''' features.<br> '''PCD''' - Personal Computing Device, a laptop, but with added extras.<br> '''FSL''' - A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software.<br> '''FOSS''' - Free and Open Source Software<br> '''GNU - GPL'''  - GNU is Not Unix, General Public Licence<br> '''EOMA''' - Embedded Open Modular Architecture<br> '''RISC-V''' - '''The Free and Open RISC Instruction Set Architecture''' '''RISC-V''' is a free and open '''ISA''' enabling a new era of processor innovation through open standard collaboration.<br> '''RISC-V ISA''' delivers a new level of free, extensible software and hardware freedom on architecture, paving the way for the next 50 years of computing design and innovation.<br> '''ISA''' - Instruction Set Architecture<br> '''RISC''' - Reduced Instruction Set Computer<br> '''SoC''' - System-on-the-Chip. One CPU to rule them all.<br> '''SoM''' - System-on-a-Module. Systems on a module consists of more '''CPU''' units and are exchangable.<br> Think of a card that can be plugged in or taken out.<br> '''GPIO''' - General Purpose Input Output<br> '''CC''' - Creative Commons<br> '''CC-BY-SA''' - Creative Commons Attribution–ShareAlike License<br> '''ETQ''' - Excellence Through Quality<br> '''OLPC''' - One Laptop Per Child a6b7ac1e4b9cf6f50ff8df134ef1d40a94a7f63c 101 100 2019-09-05T05:26:41Z Harv 2 wikitext text/x-wiki '''OS''' - Operating System<br> '''SW''' - Software<br> '''HW''' - Hardware<br> '''CPU''' - Central Processing Unit. A very small pile of interconnected transistors that go off or on and process the incoming instructions requests.<br> '''RAM''' - Random Access Memory. It can be written to, read from and erased too.<br> Bigger it is, better it is for the '''CPU''' and '''OS'''. And user.<br> '''ROM''' - Read Only Memory. It can not be written to by user or '''OS'''. Usually contains an instruction set.<br> '''BIOS''' - Basic Input Output System. When device is powered on it checks its physical integrity and various settings before it boots into '''OS'''.<br> It can be flushed and updated for better performance and additional '''HW''' features.<br> '''PCD''' - Personal Computing Device, a laptop, but with added extras.<br> '''FSL''' - A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software.<br> '''FOSS''' - Free and Open Source Software<br> '''GNU - GPL'''  - GNU is Not Unix, General Public Licence<br> '''EOMA''' - Embedded Open Modular Architecture<br> '''RISC-V''' - '''The Free and Open RISC Instruction Set Architecture''' '''RISC-V''' is a free and open '''ISA''' enabling a new era of processor innovation through open standard collaboration.<br> '''RISC-V ISA''' delivers a new level of free, extensible software and hardware freedom on architecture, paving the way for the next 50 years of computing design and innovation. That is what '''BPCD''' is all about.<br> '''ISA''' - Instruction Set Architecture<br> '''RISC''' - Reduced Instruction Set Computer<br> '''SoC''' - System-on-the-Chip. One '''CPU''' to rule them all.<br> '''SoM''' - System-on-a-Module. Systems on a module consists of more '''CPU''' units and are exchangable.<br> Think of a card that can be plugged in or taken out.<br> '''GPIO''' - General Purpose Input Output<br> '''CC''' - Creative Commons<br> '''CC-BY-SA''' - Creative Commons Attribution–ShareAlike License<br> '''ETQ''' - Excellence Through Quality<br> '''OLPC''' - One Laptop Per Child 401b5e72576e9b4a72f6f1f28c6e0a78df268502 0 5 58 40 2019-09-03T04:58:46Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' low-latency kernel for '''RISC-V'''.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components. Think quiet.<br>   '''Boot and sleep''' - fast boot time, as nobody and especially children has/have the time to wait. Ever since '''C64/AMIGA''' times computers should be also able to be switched on/off fast, so using libreboot/coreboot BIOS for embedded should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring second '''SoC/SoM''' attachment port or a slot.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br>   '''LEGO® Power Functions''' - a connector for powering and the control of actuators. '''Power Functions''' connector can be used to recharge a battery using '''LEGO®''' or similar photovoltaic sets with extra '''Power Functions''' adapter.<br>   '''RJ-12 LEGO®''' - “a shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> '''GPIO''' - a covered, retractable and a flexible flat-ribbon cable connecting General Purpose Input Output PIN array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full ACPI specification.<br> '''Waterproof keyboard''' - with ThinkPad alike track point ball.<br> '''Multitouch pad''' - flat-flush positioned above the keyboard. It has a “Wacom” mode for the extended stylus or a finger draw and is multi finger gestures aware.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Security and privacy features:</big>'''<br> '''Five (5) hardware off/on switches'''- webcam (detachable), speakers, the microphones array (detachable), Wi-Fi and Ethernet card.<br> '''Detachable USB gender-changer dongle''' - that prevents anyone to plug in USB-anything unless it is attached and a password unlocked, also when taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield''' - shields from any external and internal electromagnetic radiation. Lead-free but not inexpensive, mind you.<br> '''A stylus''' - for multitouch-pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''LEGO® Power Functions''' adapter - for connecting external photovoltaic chargers<br> '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   8807c2729e2c9264bfe1a5eb9882f6a0d8553666 59 58 2019-09-03T05:04:49Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' low-latency kernel for '''RISC-V'''.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - fast boot time, as nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be also able to be switched on/off fast, so using Libreboot/Coreboot BIOS for embedded should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring second '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''LEGO® Power Functions''' - a connector for powering and the control of actuators. '''Power Functions''' connector can be used to recharge a battery using '''LEGO®''' or similar photovoltaic sets with extra '''Power Functions''' adapter.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 16 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full ACPI specification.<br> '''Waterproof keyboard''' - with ThinkPad alike track point ball.<br> '''Multitouch pad''' - flat-flush positioned above the keyboard. It has a “Wacom” mode for the extended stylus or a finger draw and is multi finger gestures aware.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Security and privacy features:</big>'''<br> '''Five (5) hardware off/on switches'''- webcam (detachable), speakers, the microphones array (detachable), Wi-Fi and Ethernet card.<br> '''Detachable USB gender-changer dongle''' - that prevents anyone to plug in USB-anything unless it is attached and a password unlocked, also when taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield''' - shields from any external and internal electromagnetic radiation. Lead-free but not inexpensive, mind you.<br> '''A stylus''' - for multitouch-pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''LEGO® Power Functions''' adapter - for connecting external photovoltaic chargers<br> '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   02af60fa7504a091bc94537507fc55c77d8d3aaf 60 59 2019-09-03T05:14:13Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' low-latency kernel for '''RISC-V'''.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - fast boot time, as nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be also able to be switched on/off fast, so using Libreboot/Coreboot BIOS for embedded should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring second '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''LEGO® Power Functions''' - a connector for powering and the control of actuators. '''Power Functions''' connector can be used to recharge a battery using '''LEGO®''' or similar photovoltaic sets with extra '''Power Functions''' adapter.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for LEGO® MINDSTORMS® series of actuators and sensors<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 16 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full ACPI specification.<br> '''Waterproof keyboard''' - with ThinkPad alike track point ball.<br> '''Multitouch pad''' - flat-flush positioned above the keyboard. It has a “Wacom” mode for the extended stylus or a finger draw and is multi finger gestures aware.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Five (5) hardware off/on switches''' - webcam (detachable), speakers, the microphones array (detachable), Wi-Fi and Ethernet card.<br> '''Detachable USB gender-changer dongle''' - that prevents anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield''' - shields from any external and internal electromagnetic radiation. Lead-free, adds extra weight, but not inexpensive, mind you.<br> '''A stylus''' - for multitouch-pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''LEGO® Power Functions''' adapter - for connecting external photovoltaic chargers<br> '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   605e43b6de603873fdd11b2d982522df4d4e2c8b 63 60 2019-09-03T05:39:38Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' low-latency kernel for '''RISC-V'''.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - fast boot time, as nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be also able to be switched on/off fast, so using Libreboot/Coreboot BIOS for embedded should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring second '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''LEGO® Power Functions''' - a connector for powering and the control of actuators. '''Power Functions''' connector can be used to recharge a battery using '''LEGO®''' or similar photovoltaic sets with extra '''Power Functions''' adapter.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 16 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned above the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Five (5) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable), Wi-Fi and Ethernet card.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield''' - shields from any external and internal electromagnetic radiation. Lead-free, adds extra weight, but not inexpensive, mind you.<br> '''A stylus''' - for multitouch-pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''LEGO® Power Functions''' adapter - for connecting external photovoltaic chargers<br> '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   0611ce0ff569d89c92c8beb1e8096043b5b32d3e 0 1 62 53 2019-09-03T05:24:37Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by '''RISC-V''' processor(s) open architecture that runs on <big>'''Linux OS'''</big>.<br> It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Ampere.jpg|thumb]]<br> <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps.<br> Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time.<br> Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar.<br> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 9119c30621c6796f75432f8278926f3c5367e89a 71 62 2019-09-04T18:30:24Z Harv 2 /* Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. */ wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by '''RISC-V''' processor(s) open architecture that runs on <big>'''Linux OS'''</big>.<br> It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Ampere.jpg|thumb|center]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps.<br> Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time.<br> Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar.<br> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small><br> <strong>So, why should my child want one?</strong><br> Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 3f8221b9a8fbc0a0bf2412014acaa5ff822bcd79 91 71 2019-09-04T22:59:57Z Admin 1 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by '''RISC-V''' processor(s) open architecture that runs on <big>'''Linux OS'''</big>.<br> It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Ampere.jpg|thumb|center]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps.<br> Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time.<br> Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar.<br> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small><br> '''So, why should my child want one?''' Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 1a2b5de269f8871fe7fa76df74b14597d82667d1 92 91 2019-09-04T23:18:07Z Admin 1 /* Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. */ wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by '''RISC-V''' processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Ampere.jpg|thumb|center]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and a lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps.<br> Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time.<br> Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar.<br> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small><br> '''So, why should my child want one?''' Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 7c608ce5c72841669a43f4676818286b4fb064d1 93 92 2019-09-05T00:07:49Z Admin 1 /* Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. */ wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by '''RISC-V''' processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Ampere.jpg|thumb|center]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps.<br> Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time.<br> Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar.<br> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small><br> '''So, why should my child want one?''' Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 64514ca29cbd37fa39c40dce53a32e0c1e1d29e3 98 93 2019-09-05T00:18:46Z Admin 1 /* Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. */ wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by '''RISC-V''' processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Balthazar1.png|thumb|center]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps.<br> Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time.<br> Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar.<br> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small><br> '''So, why should my child want one?''' Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. bb1de41d21aca29293fea63ab79a0c26efc12416 99 98 2019-09-05T00:19:34Z Admin 1 /* Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. */ wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by '''RISC-V''' processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Balthazar1.png|thumb|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps.<br> Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time.<br> Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar.<br> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small><br> '''So, why should my child want one?''' Education being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 2aeea1b256407b2860d228bd2a6b5eb9a7d3869b 102 99 2019-09-05T07:32:53Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by '''RISC-V''' processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Balthazar1.png|thumb|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps.<br> Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time.<br> Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar.<br> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small><br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 17cdfa5cdb518d91b21bb73e20dd802dad959c7c 107 102 2019-09-05T11:46:31Z Admin 1 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default.<br> While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines.<br> <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Balthazar1.png|thumb|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution.<br> <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong><br> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products.<br> It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age.<br> Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour.<br> '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <br> <strong>I have nothing to hide. Who should be your target group than?</strong><br> Here are some use cases and personas to which '''Balthazar''' just might appeal:<br> '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device.<br> '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools.<br> '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps.<br> Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''.<br> '''TLDR;''' <strong><big>For the children age 9-99.</big></strong><br> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong><br> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious.<br> Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time.<br> Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar.<br> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it.<br> Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem.<br> We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice.<br> So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”.<br> <strong>But... A "Cloud" is free, cool, useful and hype.</strong><br> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small><br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.)<br> Want to know more?<br> Please read the [[specifications and features]]. 0edb6305c97fcf31ff39e9ca0575b8558bb2ff6a 108 107 2019-09-05T13:12:38Z Admin 1 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Balthazar1.png|thumb|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>Ohh, so yet another '''OLPC''' thingy I can see upcoming, or what...?</strong> '''OLPC''' is dead. As a duck. It was slow, underpowered, overdesigned and a bit pretentious. Also it was not available to everyone and it was a non-intentional neo-colonial tool that succumbed to the various proprietary and commercial interests at the end of its life time. Kudos to all the people who made it and maintained it for so long and out of love. Thanks for reaching out with a good intention on educating children, but it failed to recognise that target and its purpose was to be worldwide and for all the children and enthusiasts, not just patronising African and other developing nations, so - no cigar. We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. 8fd3f292dc854e7b13aa14153bd9d0f3dcc2dbc7 0 15 64 51 2019-09-04T15:47:20Z Harv 2 wikitext text/x-wiki '''<big> === A concept and a guidelines for Aperture OS === </big> 38834a13b26f22705e851673a99f9ab6e8e81481 70 64 2019-09-04T18:28:00Z Harv 2 /* A concept and a guidelines for Aperture OS */ wikitext text/x-wiki '''<big> === A concept and a guidelines for Aperture OS === This is a design proposal for a concept on "age aperture" UI of AOS. Basic idea is that OS and its UI opens up to the child as a child's knowledge progresses using the laptop and its secure features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to explore.<br> It is aimed to be a subtle kind of a auto-parental control, but not quite so stringent, as a parental control is about the permissions and control, this enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features. 312d0cb85d1268e6f97b1ba00b717708ce24d30d 72 70 2019-09-04T18:36:53Z Harv 2 /* A concept and a guidelines for Aperture OS */ wikitext text/x-wiki '''<big> === A concept and a guidelines for Aperture OS === This is a design proposal for a concept on "age aperture" UI of AOS. Basic idea is that OS and its UI opens up to the child as a child's knowledge progresses using the laptop and its secure features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to explore.<br> [[File:AOS_security.png|thumb|center]] It is aimed to be a subtle kind of a auto-parental control, but not quite so stringent, as a parental control is about the permissions and control, this enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features. 8828b2dfbea8776191eece3754d0cd0dc7248bf6 85 72 2019-09-04T22:49:20Z Admin 1 Admin moved page [['''Aperture Operating System''']] to [[Aperture Operating System]]: too many quotes wikitext text/x-wiki '''<big> === A concept and a guidelines for Aperture OS === This is a design proposal for a concept on "age aperture" UI of AOS. Basic idea is that OS and its UI opens up to the child as a child's knowledge progresses using the laptop and its secure features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to explore.<br> [[File:AOS_security.png|thumb|center]] It is aimed to be a subtle kind of a auto-parental control, but not quite so stringent, as a parental control is about the permissions and control, this enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features. 8828b2dfbea8776191eece3754d0cd0dc7248bf6 103 85 2019-09-05T07:44:20Z Harv 2 wikitext text/x-wiki '''<big> === A concept and a guidelines for Aperture OS === This is a design proposal for a concept on "age aperture" UI of AOS. Basic idea is that OS and its UI opens up to the child as a child's knowledge progresses using the laptop and its secure features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to explore.<br> [[File:AOS_security.png|center]] It is aimed to be a subtle kind of a auto-parental control, but not quite so stringent, as a parental control is about the permissions and control, this enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features. 47114a1f54bf5d5ab535d4674f01234453ddc3d9 6 17 65 2019-09-04T15:48:04Z Harv 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 18 66 2019-09-04T15:49:29Z Harv 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 19 67 2019-09-04T15:50:21Z Harv 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 20 68 2019-09-04T15:51:01Z Harv 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 21 69 2019-09-04T18:03:50Z Harv 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 8 22 73 2019-09-04T22:11:30Z Admin 1 Created page with "* about|About ** Specifications and features * mainpage|mainpage-description ** faqpage|faq ** recentchanges-url|recentchanges" wikitext text/x-wiki * about|About ** Specifications and features * mainpage|mainpage-description ** faqpage|faq ** recentchanges-url|recentchanges 1cf33f8cc9d884ef461d25b19b034bcb1b4dbc4d 74 73 2019-09-04T22:37:56Z Admin 1 wikitext text/x-wiki * about|About ** Specifications and features * mainpage|Wiki ** faqpage|faq ** recentchanges-url|recentchanges 48945fa05cb1ed4fbec18e4c9a9d5f7831ce3a03 75 74 2019-09-04T22:38:19Z Admin 1 wikitext text/x-wiki * about|About ** Specifications and features * mainpage|Wiki ** recentchanges-url|recentchanges fa3e30e9ae73974b60a218977544654fbd35419c 76 75 2019-09-04T22:39:04Z Admin 1 wikitext text/x-wiki * about|About ** Specifications and features *** '''Aperture Operating System''' * mainpage|Wiki ** recentchanges-url|recentchanges aa3d8e41b8bd22d70aadff6523ff5423f09abe54 77 76 2019-09-04T22:39:16Z Admin 1 wikitext text/x-wiki * about|About ** Specifications and features *** '''Aperture Operating System''' * mainpage|Wiki ** recentchanges-url|recentchanges e6f4df29bfb9d2225328449cbf7739c871245912 78 77 2019-09-04T22:39:29Z Admin 1 wikitext text/x-wiki * about|About ** Specifications and features ** '''Aperture Operating System''' * mainpage|Wiki ** recentchanges-url|recentchanges d0f372cae93d8227799d1d4b826b3af11fd2807b 79 78 2019-09-04T22:39:56Z Admin 1 wikitext text/x-wiki * about|About ** Specifications and features ** '''Aperture Operating System''' * mainpage|Wiki ** mainpage|Main Page ** recentchanges-url|recentchanges 6d9a34b63963bca1b86883f7dfa74838aa35636d 80 79 2019-09-04T22:40:46Z Admin 1 wikitext text/x-wiki * about|About ** Specifications and features ** '''Aperture Operating System''' * mainpage|Wiki ** mainpage|Main Page ** recentchanges-url|recentchanges ** recentfiles-url|recentfiles afd1c94b18b2af6ff3aadb24092921234b672350 81 80 2019-09-04T22:41:52Z Admin 1 wikitext text/x-wiki * about|About ** Specifications and features ** '''Aperture Operating System''' * mainpage|Wiki ** mainpage|Main Page ** recentchanges-url|recentchanges ** Special:ListFiles 2f32a7df1c4ae905992b57ab29a9833371632339 82 81 2019-09-04T22:42:08Z Admin 1 wikitext text/x-wiki * about|About ** Specifications and features ** '''Aperture Operating System''' * mainpage|Wiki ** mainpage|Main Page ** recentchanges-url|recentchanges ** Special:ListFiles|List Files f9b45cc74071e2d1bf0f6b3f4813b1917dda0f86 83 82 2019-09-04T22:43:37Z Admin 1 wikitext text/x-wiki * mainpage|About ** Specifications and features ** '''Aperture Operating System''' * mainpage|Wiki ** mainpage|Main Page ** recentchanges-url|recentchanges ** Special:ListFiles|List Files ** Special:Upload|Upload File e34d0535546d52165ec5c57f3754360dd6da46c0 84 83 2019-09-04T22:45:12Z Admin 1 wikitext text/x-wiki * mainpage|About ** Specifications and features ** '''Aperture Operating System''' ** Glossary ** User Interface * mainpage|Wiki ** mainpage|Main Page ** recentchanges-url|recentchanges ** Special:ListFiles|List Files ** Special:Upload|Upload File 807622e516b9be4c007fe642c2d56b2ba91e553c 87 84 2019-09-04T22:50:00Z Admin 1 wikitext text/x-wiki * mainpage|About ** Specifications and features ** Aperture Operating System ** Glossary ** User Interface * mainpage|Wiki ** mainpage|Main Page ** recentchanges-url|recentchanges ** Special:ListFiles|List Files ** Special:Upload|Upload File aaec23bb7d7e3c1a58c4b31e19402beafe437815 88 87 2019-09-04T22:54:25Z Admin 1 wikitext text/x-wiki * mainpage|About ** Specifications and features ** Aperture Operating System ** Glossary ** User Interface * mainpage|Wiki ** mainpage|Main Page ** recentchanges-url|recentchanges ** Special:ListFiles|List Files ** Special:Upload|Upload a File cf9a0a3b45b10f7e0848a396308dd5288fefb274 89 88 2019-09-04T22:54:49Z Admin 1 wikitext text/x-wiki * mainpage|About ** Specifications and features ** Aperture Operating System ** Glossary ** User Interface * mainpage|Wiki ** mainpage|Main Page ** recentchanges-url|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ba485471108bf8a794c898d92e6c8d00a697a342 106 89 2019-09-05T11:44:38Z Admin 1 wikitext text/x-wiki * mainpage|About ** Specifications and features ** Aperture Operating System ** User Experience ** Education ** Glossary * mainpage|Wiki ** mainpage|Main Page ** recentchanges-url|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File bdff601c01f41f3c6c7ce97c8de55225c0797ca8 4 12 90 46 2019-09-04T22:58:49Z Admin 1 wikitext text/x-wiki * Menu bar * Remove unnecessary stuff from side menu. * Mobile CSS * Color schema * Footer * URL rewriting ffd8f43004f42b456034d4d954bf4f7845936246 8 24 94 2019-09-05T00:09:20Z Admin 1 Created page with "* SEARCH * TOOLBOX * LANGUAGES" wikitext text/x-wiki * SEARCH * TOOLBOX * LANGUAGES ff01548f32b6cd4fe4e6ba4b4c9519b4b211945f 6 25 95 2019-09-05T00:17:23Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 26 96 2019-09-05T00:17:38Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 27 97 2019-09-05T00:17:54Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 28 104 2019-09-05T07:44:52Z Harv 2 Created page with "=== Education in privacy, security and a general data protection in schools, high and higher educational institutions. === Here are some examples (as in pretty pictures) why..." wikitext text/x-wiki === Education in privacy, security and a general data protection in schools, high and higher educational institutions. === Here are some examples (as in pretty pictures) why it is of an utmost importance to be well educated in security, aware of what privacy is and how to work with your data on the internet since the early age.<br> [[File:Robotic social animal.png|center|]] A humans are social animals and we like to connect to other humans, talk and share. Same as robots should do and are capable of doing. 08fb451996daefadab85c59e661c001896de1132 0 14 105 50 2019-09-05T08:05:13Z Harv 2 wikitext text/x-wiki === User Experience === A different scenarios on what BPCD could do for different users are illustrated to show what is at stake, starting from the classroom to the outdoor activities out of the schools, organisations and just an average user's environments.<br> [[File:Classroom monitor security.png|center]] A teacher is monitoring students while they play with robots. Each student's screen is also shown on the teachers display.<br> It is a feature called a "classroom control in a trusted networked environment".<br> [[File:Street security.png|center]] Young users are playing on the street on a public area in an untrusted networked environment.<br> [[File:Park security.png|center]] Afterschool activities can be performed in a city parks where there is no network. Local network can be made or an access point could be done on a mobile device. 929d76bbb367e2564a0d31895e0cce32e54b8cd8 0 13 109 49 2019-09-05T14:21:53Z Harv 2 wikitext text/x-wiki === UI guidelines for schools, education in robotics and a basic user. === c2e34b8ec0dcfdb2029a42e680e21ca1b5938966 110 109 2019-09-05T14:23:27Z Harv 2 /* UI guidelines for schools, education in robotics and a basic user. */ wikitext text/x-wiki === UI guidelines for schools, education in security, robotics and gadgets development and fpor a basic beginner user. === 57ab5ed62e7892e8c0bd2bf04a0f3a5f73835b76 111 110 2019-09-05T14:23:54Z Harv 2 /* UI guidelines for schools, education in security, robotics and gadgets development and fpor a basic beginner user. */ wikitext text/x-wiki === UI guidelines for schools, education in security, robotics and gadgets development and for a basic beginner user. === pic. abf33058a51de99a49539c05baea4a363d43f59e 6 21 112 69 2019-09-05T14:42:09Z Harv 2 Harv uploaded a new version of [[File:Park security.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 113 112 2019-09-05T14:43:00Z Harv 2 Harv reverted [[File:Park security.png]] to an old version wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 114 113 2019-09-05T14:44:27Z Harv 2 Harv reverted [[File:Park security.png]] to an old version wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 20 115 68 2019-09-05T14:46:14Z Harv 2 Harv uploaded a new version of [[File:Street security.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 18 116 66 2019-09-05T14:47:46Z Harv 2 Harv uploaded a new version of [[File:Classroom monitor security.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 29 117 2019-09-05T18:53:17Z Harv 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 1 118 108 2019-09-05T18:54:24Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> <small>You do not really read small text ever, do you?</small> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. 4655ec314ff6e505f3ba33a1bc1b190a0137ab63 121 118 2019-09-05T19:39:01Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating System''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. 1ba98b8a9577156614297c72c11ebd848cb15a55 130 121 2019-09-07T03:11:29Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. 9e429edc59135b928bb79b7be863d569a37f4eaf 136 130 2019-09-07T05:14:41Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. It is envisaged to be '''[http://GNUnet.org GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. 00d4dd72d9a19a800be7f16a5918c25955b1bc62 137 136 2019-09-07T05:28:03Z Harv 2 wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software is envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. a75f636e8869163541efd5ae17dddf4c6fba4466 138 137 2019-09-07T20:25:14Z Ziga 3 Ziga moved page [[Main Page]] to [[Balthazar]] wikitext text/x-wiki == <strong>Balthazar - a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software is envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. a75f636e8869163541efd5ae17dddf4c6fba4466 140 138 2019-09-07T20:25:28Z Ziga 3 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == <strong>''' === One laptop for the new internet. === '''</strong><br> ''' ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== '''<br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software is envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. 5b165cae46666f95621bb85c6014805a7ec7fb51 141 140 2019-09-07T20:27:07Z Ziga 3 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on <big>'''Linux OS'''</big>. It contains all the hardware and developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software is envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. 9186261d5a33402fc5af8c0b5669b62d961fa391 153 141 2019-09-07T21:27:28Z Ziga 3 /* Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. */ wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software is envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. 287af550c80159148e929bebab949ab7b552bfb5 0 14 119 105 2019-09-05T19:01:53Z Harv 2 wikitext text/x-wiki === User Experience === <strong>A different scenarios on what BPCD could do for different users are illustrated to show what is at stake, starting from the classroom to the outdoor activities out of the schools, organisations and just an average user's environments.</strong><br> [[File:Classroom monitor security.png|center]] '''A teacher is monitoring students while they play with robots. Each student's screen is also shown on the teachers display.<br> It is a feature called a "classroom control in a trusted networked environment".'''<br> [[File:Street security.png|center]] '''Young users are playing on the street on a public area in an untrusted networked environment.'''<br> [[File:Park security.png|center]] '''Afterschool activities can be performed in a city parks where there is no network. Local network can be made or an access point could be done on a mobile device.''' 9d983154d5cd1d786ae07bd1dde7833a37c344c8 120 119 2019-09-05T19:09:33Z Harv 2 /* User Experience */ wikitext text/x-wiki === User Experience === <strong><big>A different scenarios on what '''BPCD''' could do for different users are illustrated to show what is at stake, starting from the classroom to the outdoor activities out of the schools, organisations and just an average user's environments.</big></strong><br> [[File:Classroom monitor security.png|center]] <strong>A teacher is monitoring students while they play with robots.<br> Each student's screen is also shown on the teachers display.<br> It is a feature called a <big>"classroom control in a trusted networked environment".</big></strong><br> [[File:Street security.png|center]] <strong>Young users are playing on the street on a public area in an untrusted networked environment.</strong><br> [[File:Park security.png|center]] <strong>Afterschool activities can be performed in a city parks where there is no network. Local network can be made or an access point could be set on a mobile device.</strong> 4acd01a1ab02f340e428593a9410850bbc3637f9 6 17 122 65 2019-09-05T20:00:32Z Harv 2 Harv uploaded a new version of [[File:AOS security.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 123 122 2019-09-05T20:03:18Z Harv 2 Harv reverted [[File:AOS security.png]] to an old version wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 124 123 2019-09-05T20:04:43Z Harv 2 Harv reverted [[File:AOS security.png]] to an old version wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 30 125 2019-09-05T20:07:24Z Harv 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 15 126 103 2019-09-05T20:07:38Z Harv 2 wikitext text/x-wiki '''<big> === A concept and a guidelines for Aperture OS === This is a design proposal for a concept on "age aperture" UI of AOS. Basic idea is that OS and its UI opens up to the child as a child's knowledge progresses using the laptop and its secure features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to explore.<br> [[File:AOS_concept.png|center]] It is aimed to be a subtle kind of a auto-parental control, but not quite so stringent, as a parental control is about the permissions and control, this enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features. 7f1b29a10d6a4480c74ea0730d644805cb9e3186 128 126 2019-09-05T20:14:13Z Harv 2 wikitext text/x-wiki '''<big> === A concept and a guidelines for Aperture OS === This is a design proposal for a concept on "age aperture" UI of AOS. Basic idea is that '''OS''' and its '''UI''' opens up to the child as a child's knowledge progresses using '''Balthazar''' and its secure features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to explore.<br> [[File:AOS_concept.png|center]] It is aimed to be a subtle kind of a auto-parental control, but not quite so stringent, as a parental control is about the permissions and control, this enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features.<br> [[File:E_box.png]] A possible example could be "experience box" where tasks are fulfilled and a user moves on to another level with new possibilities. 44f6c457fd022499da66be764a0601a19856b9d7 129 128 2019-09-05T20:17:14Z Harv 2 wikitext text/x-wiki '''<big> === A concept and a guidelines for Aperture OS === This is a design proposal for a concept on "age aperture" UI of AOS. Basic idea is that '''OS''' and its '''UI''' opens up to the child as a child's knowledge progresses using '''Balthazar''' and its secure features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to explore.<br> [[File:AOS_concept.png|center]] It is aimed to be a subtle kind of a auto-parental control, but not quite so stringent, as a parental control is about the permissions and control, this enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features.<br> [[File:E_box.png]] A possible example could be "experience box" where tasks are fulfilled and a user moves on to another level with new possibilities, while also has enabled sharing within the trusted networks and with school colleagues. Complete process is encrypted and secure. b07f43e842ea1c8d12be2612e9a0067a26f530cd 131 129 2019-09-07T03:12:55Z Harv 2 /* A concept and a guidelines for Aperture OE */ wikitext text/x-wiki '''<big> === A concept and a guidelines for Aperture OE === This is a design proposal for a concept on "age aperture" UI of AOE. Basic idea is that '''OS''' and its '''UI''' opens up to the child as a child's knowledge progresses using '''Balthazar''' and its secure features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to explore.<br> [[File:AOS_concept.png|center]] It is aimed to be a subtle kind of a auto-parental control, but not quite so stringent, as a parental control is about the permissions and control, this enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features.<br> [[File:E_box.png]] A possible example could be "experience box" where tasks are fulfilled and a user moves on to another level with new possibilities, while also has enabled sharing within the trusted networks and with school colleagues. Complete process is encrypted and secure. 57283970e078e05566ef2bf99761f738cf4377ec 6 31 127 2019-09-05T20:12:36Z Harv 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 32 132 2019-09-07T03:17:03Z Harv 2 Created page with "=== A concept and a guidelines for Aperture OE === This is a design proposal for a concept on "age aperture" UI of AOE. Basic idea is that '''OS''' and its '''UI''' opens up..." wikitext text/x-wiki === A concept and a guidelines for Aperture OE === This is a design proposal for a concept on "age aperture" UI of AOE. Basic idea is that '''OS''' and its '''UI''' opens up to the child as a child's knowledge progresses using '''Balthazar''' and its secure features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to explore.<br> [[File:AOS_concept.png|center]] It is aimed to be a subtle kind of a auto-parental control, but not quite so stringent, as a parental control is about the permissions and control, this enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features.<br> [[File:E_box.png]] A possible example could be "experience box" where tasks are fulfilled and a user moves on to another level with new possibilities, while also has enabled sharing within the trusted networks and with school colleagues. Complete process is encrypted and secure. 77547f0b6c48b4fb5f4086b689b08530eff2e904 151 132 2019-09-07T21:25:25Z Ziga 3 Ziga moved page [['''Aperture Operating Environment''']] to [[Aperture Operating Environment]]: Too many quotes ;) wikitext text/x-wiki === A concept and a guidelines for Aperture OE === This is a design proposal for a concept on "age aperture" UI of AOE. Basic idea is that '''OS''' and its '''UI''' opens up to the child as a child's knowledge progresses using '''Balthazar''' and its secure features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to explore.<br> [[File:AOS_concept.png|center]] It is aimed to be a subtle kind of a auto-parental control, but not quite so stringent, as a parental control is about the permissions and control, this enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features.<br> [[File:E_box.png]] A possible example could be "experience box" where tasks are fulfilled and a user moves on to another level with new possibilities, while also has enabled sharing within the trusted networks and with school colleagues. Complete process is encrypted and secure. 77547f0b6c48b4fb5f4086b689b08530eff2e904 4 12 133 90 2019-09-07T03:35:14Z Harv 2 wikitext text/x-wiki * Menu bar * Remove unnecessary stuff from side menu. * Mobile CSS * Color schema * Footer * URL rewriting * Move search bar or incorporate it in the menu bar * enable media gallery - tweak and such * remove unused pages, images - clean means lean * logo, logo,logo - how "The Queen" succeeded? Freddy made a logo. * let us concentrate to security and a privacy and old/new stuff - such as GNU.net and other initiatives. * links - cool stuff * partners? ecosystem? * ETQ excellence through quality - LEGO claims: "Only the best is good enough." Crusty the Clown claims: "It is not just good. It is good enough." 06a4b9540f050090138e1ac087e78ae1101d51d0 134 133 2019-09-07T03:35:55Z Harv 2 wikitext text/x-wiki * Menu bar * Remove unnecessary stuff from side menu. * Mobile CSS * Color schema * Footer * URL rewriting * Move search bar or incorporate it in the menu bar * enable media gallery - tweak and such * remove unused pages, images - clean means lean * logo, logo,logo - how "The Queen" succeeded? Freddy made a logo. * let us concentrate to security and a privacy and old/new stuff - such as GNU.net and other initiatives. * links - cool stuff * partners? ecosystem? * ETQ excellence through quality - LEGO claims: "Only the best is good enough."<br> Crusty the Clown claims: "It is not just good. It is good enough." d764d2f894116d233c5cbaa5fa40a58a207e505e 135 134 2019-09-07T03:47:20Z Harv 2 wikitext text/x-wiki * Menu bar * Remove unnecessary stuff from side menu. * Mobile CSS * Color schema * Footer * URL rewriting * Move search bar or incorporate it in the menu bar * enable media gallery - tweak and such * remove unused pages, images - clean means lean * logo, logo,logo - how "The Queen" succeeded? Freddy made a logo. * let us concentrate to security and a privacy and old/new stuff - such as GNU.net and other initiatives. * links - cool stuff * partners? ecosystem? * ETQ excellence through quality - LEGO claims: "Only the best is good enough."<br> Crusty the Clown claims: "It is not just good. It is good enough."<br> S.Jobs: Let’s go invent tomorrow rather than worrying about what happened yesterday. 70a9dd8b00776cd98fdc31c1f8b983622cbf5571 154 135 2019-09-07T21:49:29Z Ziga 3 wikitext text/x-wiki * Menu bar * Remove unnecessary stuff from side menu. * Mobile CSS * Color schema * Footer * URL rewriting * Move search bar or incorporate it in the menu bar * enable media gallery - tweak and such * remove unused pages, images - clean means lean * logo, logo,logo - how "The Queen" succeeded? Freddie made a logo. And he sang real well. * let us concentrate to security and a privacy and old/new stuff - such as GNU.net and other initiatives. * links - cool stuff * partners? ecosystem? * ETQ excellence through quality - LEGO claims: "Only the best is good enough."<br> Crusty the Clown claims: "It is not just good. It is good enough."<br> S.Jobs: Let’s go invent tomorrow rather than worrying about what happened yesterday. 8a052393af4e9356f8a8fea04e534c7d51ed8897 155 154 2019-09-07T21:50:54Z Ziga 3 wikitext text/x-wiki * Menu bar * Remove unnecessary stuff from side menu ✔️ * Mobile CSS ✔️ * Color schema * Footer * URL rewriting ✔️ * Move search bar or incorporate it in the menu bar ✔️ * enable media gallery - tweak and such * remove unused pages, images - clean means lean * logo, logo,logo - how "The Queen" succeeded? Freddie made a logo. And he sang real well. * let us concentrate to security and a privacy and old/new stuff - such as GNU.net and other initiatives. * links - cool stuff * partners? ecosystem? * ETQ excellence through quality - LEGO claims: "Only the best is good enough."<br> Crusty the Clown claims: "It is not just good. It is good enough."<br> S.Jobs: Let’s go invent tomorrow rather than worrying about what happened yesterday. 61d2fd2fb47425a0590d59c18402f3618b5c8ba2 159 155 2019-09-08T06:35:10Z Harv 2 wikitext text/x-wiki * Menu bar * Remove unnecessary stuff from side menu ✔️ * Mobile CSS ✔️ * Color schema * Footer * URL rewriting ✔️ * Move search bar or incorporate it in the menu bar ✔️ * enable media gallery - tweak and such * remove unused pages, images - clean means lean * logo, logo,logo - how "The Queen" succeeded? Freddie made a logo. And he sang real well. A Black Hat is a no go area, while funny it is understood within the community as a negative. More options please ...and BH must go. * let us concentrate to security and a privacy and old/new stuff - such as GNU.net and other initiatives. * links - cool stuff * partners? ecosystem? * ETQ excellence through quality - LEGO claims: "Only the best is good enough."<br> Crusty the Clown claims: "It is not just good. It is good enough."<br> S.Jobs: Let’s go invent tomorrow rather than worrying about what happened yesterday. c82de8e4a15c9a626e5991ef353c7bcb2d77e18a 0 33 139 2019-09-07T20:25:14Z Ziga 3 Ziga moved page [[Main Page]] to [[Balthazar]] wikitext text/x-wiki #REDIRECT [[Balthazar]] 94039f55c5456ae01bb4d53dccb68b71a2130b13 8 24 142 94 2019-09-07T21:09:05Z Ziga 3 wikitext text/x-wiki mainpage * SEARCH * TOOLBOX * LANGUAGES 45bf9927a6939a3cc7d82e46ac67a9a81dfb1ff5 143 142 2019-09-07T21:09:20Z Ziga 3 wikitext text/x-wiki * SEARCH * TOOLBOX * LANGUAGES ff01548f32b6cd4fe4e6ba4b4c9519b4b211945f 144 143 2019-09-07T21:10:39Z Ziga 3 wikitext text/x-wiki * navigation ** mainpage|mainpage ** Special:RecentChanges|Recent changes * new heading ** portal-url|portal ** http://www.mediawiki.org|MediaWiki home * SEARCH * TOOLBOX * LANGUAGES 0c3e9eac7931c1fb46516e8fe81016dcd9fbfff1 145 144 2019-09-07T21:12:11Z Ziga 3 wikitext text/x-wiki * mainpage|About ** Specifications and features ** Aperture Operating System ** User Experience ** Education ** Glossary * SEARCH * TOOLBOX * LANGUAGES 83dbf18d3bc31b3710479e9c34a71f02c72587b3 146 145 2019-09-07T21:12:27Z Ziga 3 wikitext text/x-wiki * mainpage|About ** Specifications and features ** Aperture Operating System ** User Experience ** Education ** Glossary * SEARCH * TOOLBOX * LANGUAGES 35449eb606e60cee5867d079ef52c4fdf86bf379 147 146 2019-09-07T21:13:08Z Ziga 3 wikitext text/x-wiki * navigation ** mainpage|mainpage ** Special:RecentChanges|Recent changes * new heading ** portal-url|portal ** http://www.mediawiki.org|MediaWiki home * SEARCH * TOOLBOX * LANGUAGES 0c3e9eac7931c1fb46516e8fe81016dcd9fbfff1 148 147 2019-09-07T21:14:01Z Ziga 3 wikitext text/x-wiki * navigation ** balthazar|Balthazar * Wiki ** Special:RecentChanges|Recent changes * SEARCH * TOOLBOX * LANGUAGES 3a604d45aa90b95e179737a952a26a08a2aa5032 149 148 2019-09-07T21:15:22Z Ziga 3 wikitext text/x-wiki * navigation ** balthazar|Balthazar * Wiki ** Special:RecentChanges|Recent changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File * SEARCH * TOOLBOX * LANGUAGES 2e5d12ba5480cd4f9344136feee04c610b713fd5 150 149 2019-09-07T21:19:12Z Ziga 3 wikitext text/x-wiki * navigation ** balthazar|About * Wiki ** Special:RecentChanges|Recent changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File * SEARCH * TOOLBOX * LANGUAGES 647ebd738c26c15e163234e5e9c6ce118524b953 0 5 156 63 2019-09-08T05:27:38Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' low-latency kernel for '''RISC-V'''.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - fast boot time, as nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be also able to be switched on/off fast, so using Libreboot/Coreboot BIOS for embedded should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring second '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 16 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned above the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> <big>Additional adapter with onboard:</big><br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   bbc912c41a55f956433975f19a3e9a76a15aab64 157 156 2019-09-08T05:34:13Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' low-latency kernel for '''RISC-V'''.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a passive cooling adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - fast boot time, as nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be also able to be switched on/off fast, so using Libreboot/Coreboot BIOS for embedded should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring second '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 16 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned above the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   2a825da55c93ac217e63a516d466a363eeb081b1 158 157 2019-09-08T06:32:34Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble. We put in maximum possible '''RAM''' and we use fastest clock speeds to achieve the best possible computing performance. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-400''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty. In any case we look and listen into NVIDIA and CUDA options, accelerating totally open documentation from NVIDIA's side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - fast boot time, as nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be also able to be switched on/off fast, so using Libreboot/Coreboot BIOS attitude for embedded should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring second '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 16 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   62ca213efadbf251ae3aaae461dc92edac699a97 4 12 160 159 2019-09-08T06:36:42Z Harv 2 wikitext text/x-wiki * Menu bar * Remove unnecessary stuff from side menu ✔️ * Mobile CSS ✔️ * Color schema * Footer * URL rewriting ✔️ * Move search bar or incorporate it in the menu bar ✔️ * enable media gallery - tweak and such * remove unused pages, images - clean means lean * logo, logo,logo - how "The Queen" succeeded? Freddie made a logo. And he sang real well. A Black Hat is a no go area, while funny it is understood within the community as a negative. More options please ...and BH must go sooner the better, as more people check the page day in day out. * let us concentrate to security and a privacy and old/new stuff - such as GNU.net and other initiatives. * links - cool stuff * partners? ecosystem? * ETQ excellence through quality - LEGO claims: "Only the best is good enough."<br> Crusty the Clown claims: "It is not just good. It is good enough."<br> S.Jobs: Let’s go invent tomorrow rather than worrying about what happened yesterday. 64c311529a1d952d625380205bc0fc64a4ca4632 170 160 2019-09-08T19:18:43Z Harv 2 wikitext text/x-wiki * Menu bar * Remove unnecessary stuff from side menu ✔️ * Mobile CSS ✔️ * Color schema - distribute colors according to the 60-30-10 rule * Footer - missing stuff: transparency, financial report, who?, join us etc. in no particular order * URL rewriting ✔️ * Move search bar or incorporate it in the menu bar ✔️ * enable media gallery - tweak display and image viewing 3D and such * remove unused pages, images - clean means lean * logo, logo,logo - how "The Queen" succeeded? Freddie made a logo. And he sang real well. A Black Hat is a no go area, while funny it is understood within the community as a negative. More options please ...and BH must go sooner the better, as more people check the page day in day out. Heraldic is better than BH, but I like orange and black and green and dark neon blue :) * let us concentrate to security and a privacy and old/new stuff - such as GNU.net and other initiatives. * links - cool stuff * partners? ecosystem? * ETQ excellence through quality - LEGO claims: "Only the best is good enough."<br> Crusty the Clown claims: "It is not just good. It is good enough."<br> S.Jobs: '''Let’s go invent tomorrow rather than worrying about what happened yesterday.''' 3995eda6a26697cd9f3a01a303d099c8a3e8be28 0 1 161 153 2019-09-08T07:59:46Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on Libreswan is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. 50d8151bb843395debee13dafa62c26b8f8c1790 166 161 2019-09-08T16:23:29Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. 297b040b2e74d56761f4f6e873f8a518fd0f4e78 167 166 2019-09-08T17:48:26Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A "Cloud" is free, cool, useful and hype.</strong> Remember - a “Cloud” is just other people’s or corporations’ computers that store your data when you do "share" your stuff with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where BPCD could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data, moreover on-board but retractable '''LEGO®''' specific RJ-12, Power Functions and GPIO connectors module enables users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. ('''LEGO®''', '''Matrix''', '''VeX''', '''Arduino''' etc.) Want to know more?<br> Please read the [[specifications and features]]. bc362a445f8526341345f4ac7584b09976fd73e6 168 167 2019-09-08T17:56:59Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, governmental and public institution's workers''' that need hardware and software features to prevent an intrusion and are skilled and aware enough, so they can use all the built in hardware and software features and use additional encryption for the prevention of official and personal data-theft protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed children and schools oriented [[User Interface]] and [[User Experience]] is utilising '''Linux''' based age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser Workbench that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. Want to know more?<br> Please read the [[specifications and features]]. f284091bba61e2b713712acb506fd26fb1ed8364 169 168 2019-09-08T18:09:08Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''AOE''' for children and schools mode oriented [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser '''Workbench''' that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why should my child want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. Want to know more?<br> Please read the [[specifications and features]]. 99fb27de83db69c74feb74a6f8499dd38f1d2997 171 169 2019-09-08T19:31:26Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''AOE''' for children and schools mode oriented [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']] and features secure online in-the-browser '''Workbench''' that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. Want to know more?<br> Please read the [[specifications and features]]. ff4fa07e66b81d926a978d88c5a02149d7d30954 172 171 2019-09-08T19:42:19Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''AOE''' for children and schools mode oriented [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']] and features fully functional secure on-line and off-line in a [https://webkit.org/project/ '''Webkit'''] or [https://www.chromium.org/blink '''Blink'''] based browser, a '''Workbench''' that has fully customizable productivity apps. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. Want to know more?<br> Please read the [[specifications and features]]. dc62a703cb9949e48ca22c8c1e1507b2e6ee93ce 173 172 2019-09-08T19:58:21Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''AOE''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use it features a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser incorporated '''[http://desktop.ljudmila.net/ Workbench]'''<small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> that has a range of fully customizable productivity apps, such as Text Editor, Developer a Paint and SVG GFX creation amongst others. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. Want to know more?<br> Please read the [[specifications and features]]. b08f70314273d90d95b2888e7ed3eae0c9254c22 174 173 2019-09-08T20:02:41Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''AOE''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser incorporated '''[http://desktop.ljudmila.net/ Workbench]'''<small><br> (a '''WARNING''' - '''not''' a '''secure''' page)</small> that will have a range of fully customizable productivity apps, such as Text Editor, Developer, Paint and SVG editor amongst the other examples there. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. Want to know more?<br> Please read the [[specifications and features]]. 75ccc9d3d88c4343d93288150d67da707fd53516 175 174 2019-09-08T20:04:01Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''AOE''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated '''[http://desktop.ljudmila.net/ Workbench]'''<small><br> (a '''WARNING''' - '''not''' a '''secure''' page)</small> that will have a range of fully customizable productivity apps, such as Text Editor, Developer, Paint and SVG editor amongst the other examples there. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. Want to know more?<br> Please read the [[specifications and features]]. c6c839cba244d0fd916f63a97ec77fa595e06075 176 175 2019-09-08T20:07:31Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''AOE''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text Editor, Developer, Paint and SVG editor amongst the other examples shown. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. Want to know more?<br> Please read the [[specifications and features]]. 28697c7c48c4a97004feb03fc5e66401b4602fee 177 176 2019-09-08T20:26:23Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, Web Developer, Paint and SVG editors amongst the other examples shown. This Workbench is meant to be based on a WebOS Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. Want to know more?<br> Please read the [[specifications and features]]. 3238399980f689cea772807493a7fd90587ef048 178 177 2019-09-08T20:31:09Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. '''TLDR;''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. Want to know more?<br> Please read the [[specifications and features]]. a69cc1b10086e46a4544d4901d06c456339ccebc 185 178 2019-09-10T11:45:35Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. '''TL;DR''' <strong><big>For the children age 9-99.</big></strong> <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. Want to know more?<br> Please read the [[specifications and features]]. 50334177ad4a2ba876e314923c78f9f3b952bd69 186 185 2019-09-10T11:47:21Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. '''TL;DR''' <strong><big>'''For the children age 9-99.'''</big></strong> Want to know more?<br> Please read the [[specifications and features]]. ac1b87c8e2476e8774982fcf489bbdc888bcc4ef 187 186 2019-09-11T18:10:22Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. '''TL;DR''' <strong><big>'''For the children age 9-99.'''</big></strong> Want to know more?<br> Please read the [[specifications and features]]. 81922520904d389a7e519405a52f880e75b40a7c 188 187 2019-09-11T18:26:39Z Harv 2 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. '''TL;DR''' <strong><big>'''For all children age 9-99.'''</big></strong> Want to know more?<br> Please read the [[specifications and features]]. 7fe49a9988350eae01712c023991e69f7e2b4aa7 196 188 2019-09-16T18:12:20Z Ziga 3 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''TL;DR''' <strong><big>'''For all children age 9-99.'''</big></strong> Want to know more?<br> Please read the [[specifications and features]]. d8512c62e5ea8c2089dfc2d2def5ec6197540884 198 196 2019-09-16T18:12:37Z Admin 1 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <strong><big>'''For all children age 9-99.'''</big></strong> Want to know more?<br> Please read the [[specifications and features]]. b68f4dbb3f729760b99901c2bdf0348865b00857 199 198 2019-09-16T18:13:46Z Admin 1 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[specifications and features]]. 48e002460384233eb9db5ef1e3acd19ce9b7b610 202 199 2019-09-16T18:15:24Z Admin 1 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ]] and the [[specifications and features]]. 182445f4381c3e1643f3bcd86a02e3c2d43129b0 206 202 2019-09-16T18:27:26Z Ziga 3 wikitext text/x-wiki == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === # To enable end user to be careful and aware with their own personal data or a company data. In today’s internet age we need to know how to handle and use data protection, privacy and security, and additional physical and software safety bubble is a necessity. # To run fully open source software stack, preferably a derivative of Debian GNU/Linux. This makes a large software library instantly available and provides updates. This can also be used as a base for “custom OS”, but not mandatory. # To design inexpensive and innovative HW/SW where necessary and to use existing FOSS systems off-the shelf, partnering in a process with for an example The Libre-RISC-V SoC development or Arbor ARM based SoM. (System on the Chip or System on the Module), both supporting Linux Operating System - OS # To lead by example for other HW/SW manufacturers to open towards FOSS because we need more inexpensive laptops anyway. (300 Euros retail price point - or at maximum 100 Euros Manufacture Production Costs - MPC, volume pending) # To support low income communities all over the planet, partnering with “humaine” corporations that will give-away/rent/borrow HW/SW packages to those who are unable to afford it. (LEGO® Education, Google, various other foundations and EU initiatives). # To make computing more sustainable and reach eco friendly footprint # To make granulated product that can be configured and upgraded at an affordable price. # To make an educational product, as well as advanced computer user device. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ]] and the [[specifications and features]]. ae3c86c59a10c813ad4f0e9099344ed9fcaa4f76 207 206 2019-09-16T18:29:50Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === # To enable end user to be careful and aware with their own personal data or a company data. In today’s internet age we need to know how to handle and use data protection, privacy and security, and additional physical and software safety bubble is a necessity. # To run fully open source software stack, preferably a derivative of Debian GNU/Linux. This makes a large software library instantly available and provides updates. This can also be used as a base for “custom OS”, but not mandatory. # To design inexpensive and innovative HW/SW where necessary and to use existing FOSS systems off-the shelf, partnering in a process with for an example The Libre-RISC-V SoC development or Arbor ARM based SoM. (System on the Chip or System on the Module), both supporting Linux Operating System - OS # To lead by example for other HW/SW manufacturers to open towards FOSS because we need more inexpensive laptops anyway. (300 Euros retail price point - or at maximum 100 Euros Manufacture Production Costs - MPC, volume pending) # To support low income communities all over the planet, partnering with “humaine” corporations that will give-away/rent/borrow HW/SW packages to those who are unable to afford it. (LEGO® Education, Google, various other foundations and EU initiatives). # To make computing more sustainable and reach eco friendly footprint # To make granulated product that can be configured and upgraded at an affordable price. # To make an educational product, as well as advanced computer user device. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ]] and the [[specifications and features]]. df988e9daee22162e7105fbc3e610f13adb6592b 208 207 2019-09-16T18:35:52Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === # To enable end user to be careful and aware with their own personal data or a company data. In today’s internet age we need to know how to handle and use data protection, privacy and security, and additional physical and software safety bubble is a necessity. # To run fully open source software stack, preferably a derivative of Debian GNU/Linux. This makes a large software library instantly available and provides updates. This can also be used as a base for “custom OS”, but not mandatory. # To design inexpensive and innovative HW/SW where necessary and to use existing FOSS systems off-the shelf, partnering in a process with for an example The Libre-RISC-V SoC development or Arbor ARM based SoM. (System on the Chip or System on the Module), both supporting Linux Operating System # To lead by example for other HW/SW manufacturers to open towards FOSS because we need more inexpensive laptops anyway. (300 Euros retail price point - or at maximum 100 Euros Manufacture Production Costs - MPC, volume pending) # To support low income communities all over the planet, partnering with “humaine” corporations that will give-away/rent/borrow HW/SW packages to those who are unable to afford it. (LEGO® Education, Google, various other foundations and EU initiatives). # To make computing more sustainable and reach eco friendly footprint # To make granulated product that can be configured and upgraded at an affordable price. # To make an educational product, as well as advanced computer user device. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ]] and the [[specifications and features]]. 62ddff3bcfb98d3d1fae9b26c7096781d55ccb6a 209 208 2019-09-16T18:36:25Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === # To enable end user to be careful and aware with their own personal data or a company data. In today’s internet age we need to know how to handle and use data protection, privacy and security, and additional physical and software safety bubble is a necessity. # To run fully open source software stack, preferably a derivative of Debian GNU/Linux. This makes a large software library instantly available and provides updates. This can also be used as a base for “custom OS”, but this should not be mandatory. # To design inexpensive and innovative HW/SW where necessary and to use existing FOSS systems off-the shelf, partnering in a process with for an example The Libre-RISC-V SoC development or Arbor ARM based SoM. (System on the Chip or System on the Module), both supporting Linux Operating System # To lead by example for other HW/SW manufacturers to open towards FOSS because we need more inexpensive laptops anyway. (300 Euros retail price point - or at maximum 100 Euros Manufacture Production Costs - MPC, volume pending) # To support low income communities all over the planet, partnering with “humaine” corporations that will give-away/rent/borrow HW/SW packages to those who are unable to afford it. (LEGO® Education, Google, various other foundations and EU initiatives). # To make computing more sustainable and reach eco friendly footprint # To make granulated product that can be configured and upgraded at an affordable price. # To make an educational product, as well as advanced computer user device. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ]] and the [[specifications and features]]. 986d96b1f183987db1aa8a7725983caa1d3d3a6b 0 5 162 158 2019-09-08T08:37:07Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble. We put in maximum possible '''RAM''' and we use fastest clock speeds to achieve the best possible computing performance. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-400''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty. In any case we look and listen into NVIDIA and CUDA options, accelerating totally open documentation from NVIDIA's side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - fast boot time, as nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be also able to be switched on/off fast, so using Libreboot/Coreboot BIOS attitude for embedded should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring second '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   42254ce69441ae275bc3a07f324d8e6ef6b6e2aa 163 162 2019-09-08T10:07:54Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble. We put in maximum possible '''RAM''' and we use fastest clock speeds to achieve the best possible computing performance. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-400''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty. In any case we look and listen into NVIDIA and CUDA options, accelerating totally open documentation from NVIDIA's side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - fast boot time, as nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be also able to be switched on/off fast, so using Libreboot/Coreboot BIOS attitude for embedded should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   3b5d74e4eef48ae85ce3077e77a7f017f3a5b1ee 165 163 2019-09-08T16:13:21Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble. We also follow ARM Cortex - A77 variants along the path.<br> We put in maximum reasonable '''RAM''' and we use fastest clock speeds to achieve the best possible computing performance. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-400''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty. In any case we look and listen into NVIDIA and CUDA options, accelerating totally open documentation from NVIDIA's side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - fast boot time, as nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be also able to be switched on/off fast, so using Libreboot/Coreboot BIOS attitude for embedded should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   29488a7ae887a38c88816991288e1cab8060d913 179 165 2019-09-09T03:31:32Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble. We understand '''RISC-V''' as an ideal vehicle for the security community. We also follow '''ARM Cortex''' - '''A7X''' variants along the path if their development aligns with our expectations.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' concepts applied in a '''BPCD''' BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   9517d1252cd655c65d30ef969c86b944ea1fb510 180 179 2019-09-09T03:34:10Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble.<br> '''RISC-V''' architecture is understood as an ideal vehicle for the security community. We also follow '''ARM Cortex''' - '''A7X''' variants along the path if their development aligns with our expectations.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' concepts applied in a '''BPCD''' BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   45b562eae5c93c544692feb189bc6afc9e0a7b29 181 180 2019-09-09T03:36:44Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble.<br> '''RISC-V''' architecture is understood as an ideal vehicle for the security community.<br> We keep an eye on '''ARM Cortex''' - '''A7X''' iterations along the path waiting for their development to align with our expectations.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' concepts applied in a '''BPCD''' BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   84e0335a5921c541fe06047b54a707fd2da71a12 182 181 2019-09-09T03:58:53Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble.<br> '''RISC-V''' architecture is understood as an ideal vehicle for the security community.<br> We keep an eye on '''ARM Cortex''' - '''A7X''' iterations along the path waiting for their development to align with our expectations.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' concepts applied in a '''BPCD''' BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty).<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   5ec6634858f5187ab84a4e629d4d8f1ef34168bc 183 182 2019-09-09T03:59:34Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble.<br> '''RISC-V''' architecture is understood as an ideal vehicle for the security community.<br> We keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path waiting for their development to align with our expectations.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' concepts applied in a '''BPCD''' BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - ceramic potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw. It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done by LEGO® A/S in a multi-colour recyclable plastic with added LEGO® studs.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty).<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   7cba34ff407969fd7232dd5521ada92c098050f4 184 183 2019-09-09T07:43:41Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''Trisquel GNU''', '''Debian''' and '''Ubuntu''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble.<br> '''RISC-V''' architecture is understood as an ideal vehicle for the security community.<br> We keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path waiting for their development to align with our expectations.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' concepts applied in a '''BPCD''' BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty).<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   bb87860f3f629da906a52a5538b5ef34cc105db6 192 184 2019-09-12T23:25:11Z Ziga 3 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble.<br> '''RISC-V''' architecture is understood as an ideal vehicle for the security community.<br> We keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path waiting for their development to align with our expectations.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' concepts applied in a '''BPCD''' BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty).<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   f6258cc48b851846f9a996fbae8356170034798e 193 192 2019-09-12T23:25:52Z Ziga 3 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble.<br> '''RISC-V''' architecture is understood as an ideal vehicle for the security community.<br> We keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path waiting for their development to align with our expectations.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' concepts applied in a '''BPCD''' BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty).<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   43ea790c4846eac908979b3ef6a7f4d3328f9c0f 194 193 2019-09-12T23:27:19Z Ziga 3 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path waiting for their development to align with our expectations.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' concepts applied in a '''BPCD''' BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoC/SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000 mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Lead-free, but not inexpensive, mind you.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty).<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   bc91ff774463bc7d54ae7f3edefe97d0b52ef163 0 9 164 101 2019-09-08T10:13:47Z Harv 2 wikitext text/x-wiki '''OS''' - Operating System<br> '''SW''' - Software<br> '''HW''' - Hardware<br> '''CPU''' - Central Processing Unit. A very small pile of interconnected transistors that go off or on and process the incoming instructions requests.<br> '''RAM''' - Random Access Memory. It can be written to, read from and erased too.<br> Bigger it is, better it is for the '''CPU''' and '''OS'''. And user.<br> '''ROM''' - Read Only Memory. It can not be written to by user or '''OS'''. Usually contains an instruction set.<br> '''BIOS''' - Basic Input Output System. When device is powered on it checks its physical integrity and various settings before it boots into '''OS'''.<br> It can be flushed and updated for better performance and additional '''HW''' features.<br> '''PCD''' - Personal Computing Device, a laptop, but with added extras.<br> '''FSL''' - A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software.<br> '''FOSS''' - Free and Open Source Software<br> '''GNU - GPL'''  - GNU is Not Unix, General Public Licence<br> '''EOMA''' - Embedded Open Modular Architecture<br> '''RISC-V''' - '''The Free and Open RISC Instruction Set Architecture''' '''RISC-V''' is a free and open '''ISA''' enabling a new era of processor innovation through open standard collaboration.<br> '''RISC-V ISA''' delivers a new level of free, extensible software and hardware freedom on architecture, paving the way for the next 50 years of computing design and innovation. That is what '''BPCD''' is all about.<br> '''ISA''' - Instruction Set Architecture<br> '''RISC''' - Reduced Instruction Set Computer<br> '''SoC''' - System-on-Chip. One '''CPU''' to rule them all.<br> '''AMBA''' - '''Advanced Microcontroller Bus Architecture''' is a freely-available, open standard for the connection and management of functional blocks in a System-on-Chip.<br> '''SoM''' - System-on-Module. Systems on a module consist of one or more '''CPUs''' and '''GPUs''', but also have connectors for external peripherals and are to be easily exchangeable if put in a proper form-factor.<br> Think of a card that can be plugged in or taken out.<br> '''GPIO''' - General Purpose Input Output<br> '''CC''' - Creative Commons<br> '''CC-BY-SA''' - Creative Commons Attribution–ShareAlike License<br> '''ETQ''' - Excellence Through Quality<br> '''OLPC''' - One Laptop Per Child 8d1b36faa933f9eac95a194855e1e1ced8c058d9 8 24 189 150 2019-09-12T23:11:03Z Ziga 3 wikitext text/x-wiki * navigation ** balthazar|About * About ** Special:RecentChanges|Recent changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File * Wiki ** Special:RecentChanges|Recent changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File * SEARCH * TOOLBOX * LANGUAGES 4bc5389109dc00b8a5ac50e7a98000ffa4352b3d 190 189 2019-09-12T23:13:23Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Specifications and features|Features ** Aperture Operating Environment|Operating Environment ** User Experience ** Glossary * Wiki ** Special:RecentChanges|Recent changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File * SEARCH * TOOLBOX * LANGUAGES 04e553b4637b3fb903b69aefcb3e92d3739b66e8 191 190 2019-09-12T23:14:08Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Glossary|Glossary * Wiki ** Special:RecentChanges|Recent changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File * SEARCH * TOOLBOX * LANGUAGES 8957cafaf3c9667f98f660d051244e99d578321f 195 191 2019-09-13T18:36:46Z Admin 1 wikitext text/x-wiki * About ** Balthazar|Introduction ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** Glossary|Glossary * Wiki ** Special:RecentChanges|Recent changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File * SEARCH * TOOLBOX * LANGUAGES 8f010af1c3e824efefce1f1f835b622fef94399b 201 195 2019-09-16T18:14:49Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** FAQ|FAQ ** Glossary|Glossary * Wiki ** Special:RecentChanges|Recent changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File * SEARCH * TOOLBOX * LANGUAGES 09aee6bc69fb31983ed25a0dc57c5329e252b11e 204 201 2019-09-16T18:16:40Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** FAQ|FAQ ** Links|Links ** Glossary|Glossary * Wiki ** Special:RecentChanges|Recent changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File * SEARCH * TOOLBOX * LANGUAGES c4b92876d12d33ecac2d5fc167b32a1ed99fb3ef 0 35 197 2019-09-16T18:12:26Z Ziga 3 Created page with " <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary..." wikitext text/x-wiki <strong>Why yet another laptop?</strong><br> It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. <strong>I have nothing to hide. Who should be your target group than?</strong> Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. 040f62651f295040f1643e22c92a23686a204a41 0 36 200 2019-09-16T18:14:01Z Ziga 3 Redirected page to [[Frequently Asked Questions]] wikitext text/x-wiki #REDIRECT [[Frequently Asked Questions]] d9573c0c3747c5fcbcc255f4a5695263aa616e43 0 37 203 2019-09-16T18:16:18Z Ziga 3 Created page with "Related relevant stuff from the web..." wikitext text/x-wiki Related relevant stuff from the web... eec9aadd726a1ae1eab151b9830ed41b27072233 205 203 2019-09-16T18:17:24Z Ziga 3 wikitext text/x-wiki <big>https://www.pine64.org/pinebook-pro/</big><br> <big>http://linuxgizmos.com/sifive-launches-first-risc-v-sbc-that-runs-linux</big>/<br> <big>https://mntmn.com/reform/</big>/<br> ae3b42f360905cc34594876c0bd91af4b775831b 0 1 210 209 2019-09-17T00:14:50Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === # To enable and educate end user to be careful and aware with their own personal data, school or a company data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security.<br> Also additional physical safety features such as hardwired switches and a quickly removable peripherals are a necessity. # To run fully open source software stack, a derivative of Debian GNU/Linux free of a propriatary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory. # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example for other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation. # To support and enable low income communities and individuals all over the planet to engage in proctecting their privacy, freedoms and rights on internet. # To make computing more sustainable and reach eco friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. # To create an eco system that can promote RISC-V and ISA based computing. # To position it as an educational product, as well as an advanced computing device where its users will feel safe and sound using it. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ]] and the [[specifications and features]]. d1a5db43d149fea085ef31168b0611a8cbf7f161 211 210 2019-09-17T05:27:23Z Harv 2 /* Goals */ wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === # To enable and educate end user to be careful and aware with their own personal data, school or a company data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. # To run fully open source software stack, a derivative of Debian GNU/Linux free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory. # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example for other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation. # To support and enable low income communities and individuals all over the planet to engage in proctecting their privacy, freedoms and rights on internet. # To make computing more sustainable and reach eco friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. # To create an ecosystem that can promote RISC-V and ISA based computing. # To position it as an educational product, as well as an advanced computing device where its users will feel safe and sound using it. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ]] and the [[specifications and features]]. a25eccfa48350026d36ed5d1b6605cbb6980c269 215 211 2019-09-19T17:55:18Z Harv 2 /* Goals */ wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ]] and the [[specifications and features]]. d305c005b1b2742170b8a3e12a233b6a82f4398c 224 215 2019-09-19T18:31:17Z Admin 1 /* Goals */ wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. fe9e21c8ffef3f05cf921fccdea6abec6ff53de2 239 224 2019-10-09T18:45:36Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. de2a18527ffeb47229e740d04ff5514c565ea77d 240 239 2019-10-09T18:48:46Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also strictly follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. 32733f6884ac49e02c38501912686f4bdd6f9760 241 240 2019-10-22T03:19:05Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. 9aa1b98f5c415261addf48dd2b80a0b4623610cc 244 241 2019-10-26T06:00:50Z Harv 2 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. 0644cada2400c329e5bee4dead99ac3faabaa616 252 244 2019-11-05T20:43:47Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. <center>supported by</center> <center>[[Image:nlnet_banner.png|112px]]</center> 32eff64e5f6ec30e7e1596a587f9ddb2da1ad604 253 252 2019-11-05T20:47:05Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. <center>supported by</center> <center>[[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] [[Image|NGI0_tag.png|112px|link=https://ngi.eu]]</center> e2f453e792ebadc93512eea3fc0c481f0d8dd741 254 253 2019-11-05T20:47:41Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. <center>supported by</center> <center> [[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] [[Image:NGI0_tag.png|112px|link=https://ngi.eu]] </center> df7f06469d2663b870aba8f63a8671fad29609e4 255 254 2019-11-05T20:48:13Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. <center>supported by</center> <br> <center> [[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] &nbsp;&nbsp;&nbsp;&nbsp; [[Image:NGI0_tag.png|112px|link=https://ngi.eu]] </center> 11b0ea68134d6cc9e7ef80561b6506b715445c51 256 255 2019-11-05T20:48:26Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. <center>supported by</center> <center> [[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] &nbsp;&nbsp;&nbsp;&nbsp; [[Image:NGI0_tag.png|112px|link=https://ngi.eu]] </center> 21c7be4900f0c99cb3510b3f8a40f7923acc7fef 258 256 2019-11-05T20:52:21Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. <center>supported by</center> <br> <center> [[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] &nbsp;&nbsp;&nbsp;&nbsp; [[Image:NGI0_tag.png|112px|link=https://ngi.eu]] </center> 8167169af82badd21042638ab60dc0def816436e 259 258 2019-11-05T20:52:39Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[File:Bpcd1 sketch.png|center|Artist's conception]] === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. <br> <center>supported by</center> <center> [[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] &nbsp;&nbsp;&nbsp;&nbsp; [[Image:NGI0_tag.png|112px|link=https://ngi.eu]] </center> f2f1e20a8292dac706a69b84de303ebeeb80420a 4 12 212 170 2019-09-17T07:10:30Z Harv 2 wikitext text/x-wiki * WE NEED MAIL ADDRESSES. info,hw, sw -> @balthazar.space, -> ziga@balthazar.space, harv@balthazar.space, gizmo@balthazar.space * Menu bar * Remove unnecessary stuff from side menu ✔️ * Mobile CSS ✔️ * Color schema - distribute colors according to the 60-30-10 rule * Footer - missing stuff: transparency, financial report, who?, join us etc. in no particular order * URL rewriting ✔️ * Move search bar or incorporate it in the menu bar ✔️ * enable media gallery - tweak display and image viewing 3D and such * remove unused pages, images - clean means lean * logo, logo,logo - how "The Queen" succeeded? Freddie made a logo. And he sang real well. A Black Hat is a no go area, while funny it is understood within the community as a negative. More options please ...and BH must go sooner the better, as more people check the page day in day out. Heraldic is better than BH, but I like orange and black and green and dark neon blue :) * let us concentrate to security and a privacy and old/new stuff - such as GNU.net and other initiatives. * links - cool stuff * partners? ecosystem? * ETQ excellence through quality - LEGO claims: "Only the best is good enough."<br> Crusty the Clown claims: "It is not just good. It is good enough."<br> S.Jobs: '''Let’s go invent tomorrow rather than worrying about what happened yesterday.''' 9143e9f948177fc3ed3f729be7d80d16bd1097ff 223 212 2019-09-19T18:30:21Z Admin 1 wikitext text/x-wiki * WE NEED MAIL ADDRESSES. info,hw, sw -> @balthazar.space, -> ziga@balthazar.space, harv@balthazar.space, gizmo@balthazar.space * Menu bar * Remove unnecessary stuff from side menu ✔️ * Mobile CSS ✔️ * Color schema - distribute colors according to the 60-30-10 rule * Footer - missing stuff: transparency, financial report, who?, join us etc. in no particular order * URL rewriting ✔️ * Move search bar or incorporate it in the menu bar ✔️ * enable media gallery - tweak display and image viewing 3D and such * remove unused pages, images - clean means lean * better logo * links - cool stuff ✔️ * partners? ecosystem? e381ef95906798c8f833386e1f594e85e744ba5e 0 5 213 194 2019-09-19T04:59:12Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> In a form-factor there are some improvements in approach to physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a touchpad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key.<br> So when we say the "design is different", it actually is derived from '''IBM/Lenovo ThinkPad''' series, '''Panasonic ToughBook''' and a '''OLPC''', but improved in many important details and tailored for totally new usability experience. 10 or so years ago there were no mobile phones, but we all learned how to use them.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' concepts applied in a '''BPCD''' BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   6165aa389e81743625eff49cbb5bac236a575af0 214 213 2019-09-19T05:31:19Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> In a form-factor there are some improvements in approach to physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a touchpad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key.<br> So when we say the "design is different", it actually is derived from '''IBM/Lenovo ThinkPad''' series, '''Panasonic ToughBook''' and a '''OLPC''', but improved in many important details and tailored for totally new usability experience. 10 or so years ago there were no mobile phones, but we all learned how to use them.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' concepts applied in a '''BPCD''' BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification.<br> '''Waterproof keyboard''' - with a track-point ball.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   4ea38355183eed494b1cb03e2efa1f2257868f70 232 214 2019-10-02T08:12:38Z Admin 1 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> In a form-factor there are some improvements in approach to physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a touchpad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key.<br> So when we say the "design is different", it actually is derived from '''IBM/Lenovo ThinkPad''' series, '''Panasonic ToughBook''' and a '''OLPC''', but improved in many important details and tailored for totally new usability experience. 10 or so years ago there were no mobile phones, but we all learned how to use them.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   1d605f67c83467205557f165d0bdb3a2b90c7fea 233 232 2019-10-02T16:42:44Z Admin 1 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> In a form-factor there are some improvements in approach to physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a touchpad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key.<br> So when we say the "design is different", it actually is derived from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''' and a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''', but improved in many important details and tailored for totally new usability experience. 10 or so years ago there were no mobile phones, but we all learned how to use them.<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   ad73662798009ff22dc3d42373c006628066b0f3 234 233 2019-10-04T04:21:50Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' '''[https://nixos.org/ NixOS]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a touchpad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key.<br> So when we say the "design is different", it actually is inspired by and derived from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main security USB features by [https://www.nitrokey.com/ Nitrokey] concept. Balthazar's design aims for a totally new usability experience.<br> "10 or so years ago there were no mobile phones, but we all learned how to use them." (Arjen Kamphuis in xTED speech in Delft)<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   8e8d63fe71e7d4c99bc7f1e39956209a8bcdc40a 235 234 2019-10-04T04:23:22Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' '''[https://nixos.org/ NixOS]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''/'''ARM'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a touchpad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key.<br> So when we say the "design is different", it actually is inspired by and derived from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main security USB features by [https://www.nitrokey.com/ Nitrokey] concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   c6a34d89f3516e6d193c0370051684d7a7625f14 236 235 2019-10-05T04:55:41Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key.<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main security USB dongle features by [https://www.nitrokey.com/ Nitrokey] concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards FOSS compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   731cdb8a847823ca3c0941cbdf461babc19c69f2 237 236 2019-10-05T05:22:20Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key.<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   d2af9ea9f329cfb2d8bdc3503c065194385d3817 238 237 2019-10-07T03:04:26Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run on '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power of all I/O modules preventing any remote switch-on possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   0c2dbc3dc622a74993ceb19b28264408f87e75ed 242 238 2019-10-22T03:47:19Z Ziga 3 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power of all I/O modules preventing any remote switch-on possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   8dc06d1d77d24b81ad62684f5c3e863ead61e27e 243 242 2019-10-22T19:53:54Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power of all I/O modules preventing any remote switch-on possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   7c96bef18dc5d0c627925c1fd7af0f2270c7f85e 0 35 216 197 2019-09-19T18:07:49Z Harv 2 wikitext text/x-wiki === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. <strong>But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike!</strong> '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. ===I have nothing to hide. Who should be your target group than?=== Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. <strong>What do you really want?</strong> We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. <strong>But... A ''"Cloud"'' is free, cool, useful and hype.</strong> Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> '''So, why me or my children should want one?''' [[Education]] being a very important issue today all over the planet is yet another field where '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®''' specific RJ-12 and '''Power Functions''' connectors. 2b60f4a9b8dd4c1a0448d6bd0e293d43d4e874df 217 216 2019-09-19T18:13:28Z Harv 2 wikitext text/x-wiki === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. === But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike. === '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behavior. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. ===I have nothing to hide. Who should be your target group than?=== Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. === What do you really want? === We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behavior and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. === But... A ''"Cloud"'' is free, cool, useful and hype. === Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> === So, why me or my children should want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. 926f6777015fd011f6641dbce5bc4fe00f33b17d 218 217 2019-09-19T18:14:16Z Harv 2 /* = */ wikitext text/x-wiki === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. ===But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behavior. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. ===I have nothing to hide. Who should be your target group than?=== Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. === What do you really want? === We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behavior and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. === But... A ''"Cloud"'' is free, cool, useful and hype. === Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> === So, why me or my children should want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. 47061974689c035bb84cd84e3eb82b108c92621c 219 218 2019-09-19T18:15:58Z Harv 2 /* I have nothing to hide. Who should be your target group than? */ wikitext text/x-wiki === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. ===But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behavior. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. ===I have nothing to hide. Who should be your target group than?=== Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. === What do you really want? === We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behavior and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. === But... A ''"Cloud"'' is free, cool, useful and hype. === Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> === So, why me or my children should want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. bc99975411e60e4414e2fb16cce0312054877978 220 219 2019-09-19T18:27:40Z Admin 1 wikitext text/x-wiki === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. ===But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behavior. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. ===Who is this for?=== Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. === What do you really want? === We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behavior and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. === But... A ''"Cloud"'' is free, cool, useful and hype. === Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> === So, why me or my children should want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. 3591ffe82ce04cff915a544ec006087a7da72f1b 221 220 2019-09-19T18:28:14Z Admin 1 wikitext text/x-wiki ===Who is this for?=== Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity.<br> Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. ===But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behavior. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. === What do you really want? === We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behavior and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. === But... A ''"Cloud"'' is free, cool, useful and hype. === Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> === So, why me or my children should want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. acdf37e3ecaa98eb5d4fb2cb58f77cc94da7a99c 222 221 2019-09-19T18:28:53Z Admin 1 /* Who is this for? */ wikitext text/x-wiki ===Who is this for?=== Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity. Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. ===But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behavior. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. === What do you really want? === We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behavior and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. === But... A ''"Cloud"'' is free, cool, useful and hype. === Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> === So, why me or my children should want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. 3b13cce6da8e7d0fa4d6096686db3eeb3cbbb4f9 8 24 225 204 2019-09-23T17:48:19Z Admin 1 wikitext text/x-wiki * About ** Balthazar|Introduction ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** FAQ|FAQ ** Links|Links ** Glossary|Glossary * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES 8848cce754b05ae22f10f2ed830adfa312ae3c0d 226 225 2019-09-23T20:04:36Z Admin 1 wikitext text/x-wiki * About ** Balthazar|Introduction ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES 92c8d4bd4da68d2afdf8d34f4d1e2ad6d0d612de 0 38 227 2019-09-23T20:05:46Z Admin 1 Created page with "Send mail to [mailto:info@balthazar.space info@balthazar.space]" wikitext text/x-wiki Send mail to [mailto:info@balthazar.space info@balthazar.space] 49468de369118e94277117d318bfc98e607db9f3 228 227 2019-09-25T05:12:41Z Admin 1 wikitext text/x-wiki <center>'''Send us a mail.'''</center><br> '''General''' inquiries, suggestions and requests - [mailto:info@balthazar.space info@balthazar.space]<br> Questions and suggestions about '''hardware''' - [mailto:hw@balthazar.space hw@balthazar.space]<br> Questions and suggestions about '''software''' - [mailto:sw@balthazar.space sw@balthazar.space] eed2baa464a140c894df126eabb0fcbcb63f5a38 0 37 229 205 2019-09-25T16:47:27Z Admin 1 wikitext text/x-wiki <big>https://www.pine64.org/pinebook-pro/</big><br> <big>http://linuxgizmos.com/sifive-launches-first-risc-v-sbc-that-runs-linux</big>/<br> <big>https://mntmn.com/reform/</big>/<br> ===Basic web applications=== https://codesandbox.io/s/vanilla https://glitch.com/ f5f1f7bdbeb9879622c00467f050b535edd48867 230 229 2019-09-25T16:48:31Z Admin 1 wikitext text/x-wiki https://www.pine64.org/pinebook-pro/ http://linuxgizmos.com/sifive-launches-first-risc-v-sbc-that-runs-linux https://mntmn.com/reform/ ===Basic web applications=== https://codesandbox.io/s/vanilla https://glitch.com/ b52c8b59c573f15ed04e3d91684c7c579a3faa9b 231 230 2019-09-25T17:21:20Z Admin 1 wikitext text/x-wiki https://www.pine64.org/pinebook-pro/ http://linuxgizmos.com/sifive-launches-first-risc-v-sbc-that-runs-linux https://mntmn.com/reform/ ===Basic web applications=== https://liveweave.com/ https://codesandbox.io/s/vanilla https://glitch.com/ d07ee2da35141bc9f81a96d763845788c9cbce61 6 39 245 2019-11-01T00:29:14Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 246 245 2019-11-01T00:31:26Z Admin 1 Admin uploaded a new version of [[File:Balthazarset1.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 40 247 2019-11-01T00:55:44Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 41 248 2019-11-05T18:44:10Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 42 249 2019-11-05T18:44:24Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 43 250 2019-11-05T20:41:46Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 257 250 2019-11-05T20:51:46Z Admin 1 Admin uploaded a new version of [[File:Nlnet banner.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 44 251 2019-11-05T20:42:01Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 35 260 222 2019-11-05T21:09:45Z Admin 1 wikitext text/x-wiki ===Who is this for?=== Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity. Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [['''Aperture Operating Environment''']].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. ===But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behavior. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. === What do you really want? === We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behavior and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. === But... A ''"Cloud"'' is free, cool, useful and hype. === Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> === So, why should me or my children want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. 74016dc439ebefb80d81873740c5484aa926cad9 6 40 261 247 2019-11-05T21:13:57Z Admin 1 Admin uploaded a new version of [[File:Balthazarset2.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 293 261 2019-12-10T01:19:46Z Ziga 3 Ziga moved page [[File:Balthazarset2.png]] to [[File:BalthazarSetG1.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 295 293 2019-12-10T01:20:25Z Ziga 3 Ziga moved page [[File:BalthazarSetG1.png]] to [[File:BalthazarSet G1 1.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 5 262 243 2019-11-05T21:20:03Z Admin 1 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> [[Image:Balthazarset1.png]] '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power of all I/O modules preventing any remote switch-on possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   f820f55ee5971fd2006f1091a9efbaa2f2d8b601 263 262 2019-11-06T19:01:45Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> [[Image:Balthazarset1.png]] '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   160cbe4c8040f7b71ca238b63e7a1a01721b8ffd 264 263 2019-11-06T19:25:55Z Harv 2 wikitext text/x-wiki '''<big>Basic specifications and features</big>'''<br> [[Image:Balthazarset1.png]] '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> '''<big>Hardware security and privacy features:</big>'''<br> '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> '''<big>A few interesting extras:</big>'''<br> '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> '''<big>Additional adapter with an onboard:</big>'''<br> '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   9ad7c5edaa5a52d406ecf6b3c948532333e5f7e0 277 264 2019-11-10T22:22:22Z Admin 1 wikitext text/x-wiki ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> [[Image:Balthazarset1.png]] '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features:</big>== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras:== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard:=== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   fd843ecb2f094b0d593d3e885511e2a2bceef4d8 278 277 2019-11-10T22:22:49Z Admin 1 wikitext text/x-wiki __NOTOC__ ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> [[Image:Balthazarset1.png]] '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features:</big>== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras:== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard:=== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> '''Charms:''' '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   f92e889043d31c5d66ed8510e302fe006edc3cdb 279 278 2019-11-10T22:23:21Z Admin 1 wikitext text/x-wiki __NOTOC__ ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> [[Image:Balthazarset1.png]] '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard=== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   e8f134f2a451327ded09ed96d2c498817735f842 280 279 2019-11-10T22:23:42Z Admin 1 /* Additional adapter with an onboard= */ wikitext text/x-wiki __NOTOC__ ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> [[Image:Balthazarset1.png]] '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   11e0726cd8c02e988515a7b736a9274343da2c62 281 280 2019-11-10T22:24:02Z Admin 1 /* Basic specifications and features */ wikitext text/x-wiki __NOTOC__ ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> [[Image:Balthazarset1.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   383dc0690f60f25d0d26f78c48208744b743ba77 303 281 2019-12-10T01:23:13Z Ziga 3 wikitext text/x-wiki __NOTOC__ ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> [[Image:BalthazarSet G1 2.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Want to know more? Pretty pictures ahead.]]   f44b5be91acf249400d5b5b1f3286e5a23b0478e 0 1 265 259 2019-11-07T12:41:32Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> === Goals === A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. <br> <center>supported by</center> <center> [[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] &nbsp;&nbsp;&nbsp;&nbsp; [[Image:NGI0_tag.png|112px|link=https://ngi.eu]] </center> 78bdbdf1eae03fdb9186a09c446fa8e790417c88 266 265 2019-11-07T12:44:14Z Admin 1 /* Goals */ wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[Goals|=== Goals ===]] A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. <br> <center>supported by</center> <center> [[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] &nbsp;&nbsp;&nbsp;&nbsp; [[Image:NGI0_tag.png|112px|link=https://ngi.eu]] </center> 66974064438a8505a48d66083254363fbd713f52 268 266 2019-11-07T12:48:23Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> [[Goals|'''Goals''']] <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|Frequently asked questions]] and the [[specifications and features]]. <br> <center>supported by</center> <center> [[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] &nbsp;&nbsp;&nbsp;&nbsp; [[Image:NGI0_tag.png|112px|link=https://ngi.eu]] </center> 90fe59c836609d41b87e7745c385f33822a635c9 270 268 2019-11-07T12:57:40Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|'''Frequently asked questions''']], [[Goals|'''Goals''']] and the [[Specification and features|'''Specifications and features''']]. <br> <center>supported by</center> <center> [[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] &nbsp;&nbsp;&nbsp;&nbsp; [[Image:NGI0_tag.png|112px|link=https://ngi.eu]] </center> 66c580028a2acb05d7428f343c969c91db328cd4 271 270 2019-11-07T12:59:12Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[FAQ|'''Frequently asked questions''']], [[Goals|'''Goals''']] and the [[Specifications and features|'''Specifications and features''']]. <br> <center>supported by</center> <center> [[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] &nbsp;&nbsp;&nbsp;&nbsp; [[Image:NGI0_tag.png|112px|link=https://ngi.eu]] </center> 80c34d43f8c9f1ae2d09c7434ec88c391bca1dea 272 271 2019-11-07T13:07:08Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']] and the [[Specifications and features|'''Specifications and features''']]. <br> <center>supported by</center> <center> [[Image:nlnet_banner.png|112px|link=https://nlnet.nl]] &nbsp;&nbsp;&nbsp;&nbsp; [[Image:NGI0_tag.png|112px|link=https://ngi.eu]] </center> 7f74e210fd3adda600b72c1165ab6ae3dd068949 274 272 2019-11-10T21:05:10Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']] and the [[Specifications and features|'''Specifications and features''']]. 543440e0895d7bdc39309a4341d4ec068dfe1eab 284 274 2019-11-25T13:17:55Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[FAQ|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. 2be74566dd84876a98c74a28108c03963ff0deac 285 284 2019-11-25T13:19:14Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[News|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. 05d8158d2989a50ec0e57271bfca5827d26ef555 0 45 267 2019-11-07T12:46:18Z Admin 1 Created page with "A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age..." wikitext text/x-wiki A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. e4b58e3818f0b6e46c4f925b0a18ce1bc6a74ea3 269 267 2019-11-07T12:50:45Z Admin 1 wikitext text/x-wiki A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their own data, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> We are: # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. 0506506e49f5c7e1066a056c9bdb78cec2a4e782 273 269 2019-11-08T17:49:41Z Admin 1 wikitext text/x-wiki A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their private, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> We are: # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the process closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in procetcting their privacy, freedoms and rights on the internet. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. c50c42bb1196fa0f59eb45277ee6c579ae8a280e 8 24 275 226 2019-11-10T21:07:12Z Admin 1 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES ffdd958c1de64fb3d68422c881fd62e6bfdf8b8b 0 37 276 231 2019-11-10T21:42:44Z Admin 1 wikitext text/x-wiki https://www.pine64.org/pinebook-pro/ http://linuxgizmos.com/sifive-launches-first-risc-v-sbc-that-runs-linux https://mntmn.com/reform/ https://sugarlabs.org/ ===Basic web applications=== https://liveweave.com/ https://codesandbox.io/s/vanilla https://glitch.com/ da09658ac1f0601c0806b5c9dd5ca145804ddd30 307 276 2019-12-10T01:44:59Z Ziga 3 wikitext text/x-wiki http://linuxgizmos.com/sifive-launches-first-risc-v-sbc-that-runs-linux https://mntmn.com/reform/ ===Laptops=== https://www.pine64.org/pinebook-pro/ https://www.one-education.org/pages/infinity ===Designs=== https://sugarlabs.org/ ===Basic web applications=== https://liveweave.com/ https://codesandbox.io/s/vanilla https://glitch.com/ b87823690e8ebe24c41bb3160094761ca284419f 308 307 2019-12-10T01:46:57Z Ziga 3 wikitext text/x-wiki ===News=== http://linuxgizmos.com/ ===Buyabale Laptops=== https://www.pine64.org/pinebook-pro/ https://www.one-education.org/pages/infinity ===Designs=== https://sugarlabs.org/ https://mntmn.com/reform/ ===Web Applications=== https://liveweave.com/ https://codesandbox.io/s/vanilla https://glitch.com/ 08f61ffae00b512699927d1036e644eb9f9d4074 309 308 2019-12-10T01:47:14Z Ziga 3 wikitext text/x-wiki __NOTOC__ ===News=== http://linuxgizmos.com/ ===Buyabale Laptops=== https://www.pine64.org/pinebook-pro/ https://www.one-education.org/pages/infinity ===Designs=== https://sugarlabs.org/ https://mntmn.com/reform/ ===Web Applications=== https://liveweave.com/ https://codesandbox.io/s/vanilla https://glitch.com/ b2e57c5194d92585320b3e8364ec2b33683716b2 0 14 282 120 2019-11-17T14:27:24Z Admin 1 wikitext text/x-wiki === User Experience === == "Veronica" Secure Boot Environment == After the initial hardware initialisation sequence and after powering-on '''Balthazar''', the first '''GUI''' that is presented is '''Secure Boot Environment''' from where the user can choose encrypted boot device or a bootable volume. After password is given, '''VSBE''' allows boot sequence to be continued and the whole system is initialized. This ensures proper encryption between hardware and a currently mounted volume or a device. During the boot process the keyboard's firmware is initialized and provides secure compression of a input stream. Usual window manager's log-in dialog is presented as one more passowrd is required to finish the whole boot sequence into user's GUI desktop. '''Veronica''' sits between hardware, kernel, keyboard and a userspace and manages booting and most of the '''Balthazar''''s internal encrypted communication. == Classroom and office user-case scenarios == A different scenarios on what '''BPCD''' could do for different users are illustrated to show what is at stake, starting from the classroom to the outdoor activities out of the schools, organisations and just an average user's environments.<br> [[File:Classroom monitor security.png|center]] A teacher is monitoring students while they play with robots.<br> Each student's screen is also shown on the teachers display.<br> It is a feature called a <big>"classroom control in a trusted networked environment".</big><br> [[File:Street security.png|center]] Young users are playing on the street on a public outdoor area in an untrusted networked environment.<br> [[File:Park security.png|center]] Afterschool activities can be performed in a city parks where there is no network. Local network can be made or an access point could be set on a mobile device. 5c6eea44b0ea23a521599063d37ffc64c40fe670 0 28 283 104 2019-11-17T14:29:34Z Admin 1 wikitext text/x-wiki === Education in privacy, security and a general data protection in schools, high and higher educational institutions. === Here are some examples (as in pretty pictures) why it is of an utmost importance to be well educated in security, aware of what privacy is and how to work with your data on the internet since the early age.<br> [[File:Robotic social animal.png|center|]] A humans are social animals and we like to connect to other humans, talk and share. Same as insects, animals and even robots are capable of doing. a5a58d9a67588694c15a0fd4f27bff975725547f 0 46 286 2019-11-25T18:48:18Z Admin 1 Created page with " '''Actual news and a Balthazar development progress''' A short history of Balthazar: Development of Balthazar a..." wikitext text/x-wiki '''Actual news and a Balthazar development progress''' A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various representatives and teachers in '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. 68a5a93018e9255dc55f5a56dd3ac623e159fe0b 287 286 2019-11-26T14:13:46Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various representatives and teachers in '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. 38b3a5b756ab856bb7d97f80d82e7a7a5e310837 288 287 2019-11-27T11:16:00Z Admin 1 /* Actual news and a Balthazar development progress */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: '''April 2019''' - a day Zero, where we realised that it can be done, it should be done and we even know how. '''May 2019''' - started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. '''June 2019''' - a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. '''July 2019''' - All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from TUFTS helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to NLNET, as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. '''August 2019''' - prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of Bauhaus University in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of Charles Wuetrich and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. '''September 2019''' - A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the ESC - End of Summer Camp where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with HiTechic again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. '''October 2019''' - We did the first renders and a few design studies of the casing, but more we will discuss with LEGO Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from NETNL ina shape of technical support and a donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. '''November 2019''' - Somewhat longer emailing between SiFive and us on adopting RISC-V and ISA making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller RISC-V controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have a mutual agreement to publish it all publicly under CERN/GPL3 licences. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of EOMA68 evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from LEGO and also brief some representatives of LEGO Education on our current development. In Weimar end of November at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into CrowdSupply support and options we have there. One thing we do know for sure is - we do not want to over-promise. c16ab352e62baf65042ec38a8c0ba924bd2b70f8 289 288 2019-11-28T11:28:27Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: '''April 2019''' - a day Zero, where we realised that it can be done, it should be done and we even know how. '''May 2019''' - started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. '''June 2019''' - a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. '''July 2019''' - All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. '''August 2019''' - prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. '''September 2019''' - A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. '''October 2019''' - We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. '''November 2019''' - Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. 5db889a8768229e78f46bb4cda938bb622c17566 290 289 2019-12-07T10:39:36Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: '''April 2019''' - a day Zero, where we realised that it can be done, it should be done and we even know how. '''May 2019''' - started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. '''June 2019''' - a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. '''July 2019''' - All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. '''August 2019''' - prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. '''September 2019''' - A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. '''October 2019''' - We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. '''November 2019''' - Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. '''December 2019''' - Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. fe13094c4534dd745f2188f933a7bf105dec1375 6 42 291 249 2019-12-10T01:19:13Z Ziga 3 Ziga moved page [[File:LLaptop2.jpg]] to [[File:BalthazarSetL1 1.jpg]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 299 291 2019-12-10T01:21:17Z Ziga 3 Ziga moved page [[File:BalthazarSetL1 1.jpg]] to [[File:BalthazarSet L1 1.jpg]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 47 292 2019-12-10T01:19:13Z Ziga 3 Ziga moved page [[File:LLaptop2.jpg]] to [[File:BalthazarSetL1 1.jpg]] wikitext text/x-wiki #REDIRECT [[File:BalthazarSetL1 1.jpg]] 87c152d7b76a840ba077f3155fb5390550800d97 6 48 294 2019-12-10T01:19:46Z Ziga 3 Ziga moved page [[File:Balthazarset2.png]] to [[File:BalthazarSetG1.png]] wikitext text/x-wiki #REDIRECT [[File:BalthazarSetG1.png]] fc36bc8ba88953151083b3299964bcd28589bfd3 6 49 296 2019-12-10T01:20:25Z Ziga 3 Ziga moved page [[File:BalthazarSetG1.png]] to [[File:BalthazarSet G1 1.png]] wikitext text/x-wiki #REDIRECT [[File:BalthazarSet G1 1.png]] 7610b332b0c1d4af3f26376ea0d3a47acf544261 6 41 297 248 2019-12-10T01:20:57Z Ziga 3 Ziga moved page [[File:LLaptop1.jpg]] to [[File:BalthazarSet L1 2.jpg]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 50 298 2019-12-10T01:20:57Z Ziga 3 Ziga moved page [[File:LLaptop1.jpg]] to [[File:BalthazarSet L1 2.jpg]] wikitext text/x-wiki #REDIRECT [[File:BalthazarSet L1 2.jpg]] ed05ade68d99196068855a5febd373decbe1bbf0 6 51 300 2019-12-10T01:21:17Z Ziga 3 Ziga moved page [[File:BalthazarSetL1 1.jpg]] to [[File:BalthazarSet L1 1.jpg]] wikitext text/x-wiki #REDIRECT [[File:BalthazarSet L1 1.jpg]] 238820dd38813974ff06af8c768d36d60d86cb9c 6 39 301 246 2019-12-10T01:21:58Z Ziga 3 Ziga moved page [[File:Balthazarset1.png]] to [[File:BalthazarSet G1 2.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 52 302 2019-12-10T01:21:58Z Ziga 3 Ziga moved page [[File:Balthazarset1.png]] to [[File:BalthazarSet G1 2.png]] wikitext text/x-wiki #REDIRECT [[File:BalthazarSet G1 2.png]] fc74d0a50a0a840b72e2bd3e6036e1a0496928e1 0 53 304 2019-12-10T01:27:33Z Ziga 3 Created page with "==G1== [[Image:BalthazarSet G1 1.png]] [[Image:BalthazarSet G1 2.png]] ==L1== [[Image:BalthazarSet L1 1.jpg]] [[Image:BalthazarSet L1 2.jpg]]" wikitext text/x-wiki ==G1== [[Image:BalthazarSet G1 1.png]] [[Image:BalthazarSet G1 2.png]] ==L1== [[Image:BalthazarSet L1 1.jpg]] [[Image:BalthazarSet L1 2.jpg]] ccebce5d0ce389b7fcdc0fb6e6fd4518f0d75934 305 304 2019-12-10T01:43:36Z Ziga 3 Ziga moved page [[Prototypes]] to [[Designs]] wikitext text/x-wiki ==G1== [[Image:BalthazarSet G1 1.png]] [[Image:BalthazarSet G1 2.png]] ==L1== [[Image:BalthazarSet L1 1.jpg]] [[Image:BalthazarSet L1 2.jpg]] ccebce5d0ce389b7fcdc0fb6e6fd4518f0d75934 0 54 306 2019-12-10T01:43:36Z Ziga 3 Ziga moved page [[Prototypes]] to [[Designs]] wikitext text/x-wiki #REDIRECT [[Designs]] 451f44fd9e6c2d254bebc2fad733d26036d4de4b 0 37 310 309 2019-12-10T01:47:36Z Ziga 3 wikitext text/x-wiki __NOTOC__ ===News=== http://linuxgizmos.com/ ===Buyable Laptops=== https://www.pine64.org/pinebook-pro/ https://www.one-education.org/pages/infinity ===Designs=== https://sugarlabs.org/ https://mntmn.com/reform/ ===Web Applications=== https://liveweave.com/ https://codesandbox.io/s/vanilla https://glitch.com/ 34f1474d0a24532ab0ff9fb4ba133640a80d1006 313 310 2020-01-07T15:00:26Z Admin 1 wikitext text/x-wiki __NOTOC__ ===News=== http://linuxgizmos.com/ ===Buyable Laptops=== https://www.pine64.org/pinebook-pro/ https://www.one-education.org/pages/infinity https://slimbook.es/en/ ===Designs=== https://sugarlabs.org/ https://mntmn.com/reform/ https://www.powerpc-notebook.org/en/ ===Web Applications=== https://liveweave.com/ https://codesandbox.io/s/vanilla https://glitch.com/ bfe155c7d72d019c6841288833903ed8666fc4b8 0 55 311 2019-12-22T23:58:07Z Ziga 3 Created page with "Major parts are: * Case * Keyboard * Touchpad * Display * Power and battery * Motherboard" wikitext text/x-wiki Major parts are: * Case * Keyboard * Touchpad * Display * Power and battery * Motherboard 32b0dcbe6df5d9b5ba99f661587ed699f7458523 314 311 2020-01-07T15:34:13Z Admin 1 wikitext text/x-wiki Major parts are: * Case * Keyboard * Touchpad * Display * Power and battery * Motherboard * Software 52ae13250317b743b8dad689d9b4d3d22bc20819 315 314 2020-01-07T15:39:26Z Admin 1 wikitext text/x-wiki Major Balthazar parts are: * Case * Keyboard * Touch-pad * Display * Power and battery * Motherboard * Software a9b1c22c863a2ae6e9e6a24b68abfce18334b011 318 315 2020-01-22T21:51:33Z Ziga 3 wikitext text/x-wiki [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: * Power Controller and battery * System on a Module (the computer) * USB hub * Display Controller and panel * Case * Keyboard * Touch-pad * Software ac0a25391af94072d12a62eaf29d98119ff37c98 319 318 2020-01-22T22:03:31Z Ziga 3 wikitext text/x-wiki [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system ==System on a Module (SOM)== This is the main system board, the computer. This should be swappable among different makers, so the minimum of ports is required. Just Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports. ==Display Controller and panel== ==Case== ==Keyboard== ==Touch-pad== ==Software== b0e292512abc2afc94b285c16c6f6d0b619eed99 320 319 2020-01-22T22:05:31Z Ziga 3 wikitext text/x-wiki __NOTOC__ [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system ==System on a Module (SOM)== This is the main system board, the computer. This should be swappable among different makers. Minimum of ports is required for wider compaitibility. Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports. ==Display Controller and panel== ==Case== ==Keyboard and Touch-pad== ==Software== e7b0fa85a84b2a8852bea190b82239b517bdd45f 321 320 2020-01-22T22:06:41Z Ziga 3 /* Power Controller and battery */ wikitext text/x-wiki __NOTOC__ [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system. It should be capable enough to run some USB connected hardware, too. ==System on a Module (SOM)== This is the main system board, the computer. This should be swappable among different makers. Minimum of ports is required for wider compaitibility. Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports. ==Display Controller and panel== ==Case== ==Keyboard and Touch-pad== ==Software== 23305a06d70266e4be8a4da48e1caf9d07da8742 322 321 2020-01-22T22:08:30Z Ziga 3 /* USB hub */ wikitext text/x-wiki __NOTOC__ [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system. It should be capable enough to run some USB connected hardware, too. ==System on a Module (SOM)== This is the main system board, the computer. This should be swappable among different makers. Minimum of ports is required for wider compaitibility. Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports, which can be additionally used, but should not be required. At least USB 2 or better. ==Display Controller and panel== ==Case== ==Keyboard and Touch-pad== ==Software== c3e5fb17fa1f8022af1e319dc4f70ee20af02d0b 323 322 2020-01-22T22:13:15Z Ziga 3 /* System on a Module (SOM) */ wikitext text/x-wiki __NOTOC__ [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system. It should be capable enough to run some USB connected hardware, too. ==System on a Module (SOM)== This is the main system board, the computer. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports, which can be additionally used, but should not be required. At least USB 2 or better. ==Display Controller and panel== ==Case== ==Keyboard and Touch-pad== ==Software== 57373d5677a1b64cbf5e5e354638249c2b541c18 324 323 2020-01-22T22:15:46Z Ziga 3 /* Display Controller and panel */ wikitext text/x-wiki __NOTOC__ [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system. It should be capable enough to run some USB connected hardware, too. ==System on a Module (SOM)== This is the main system board, the computer. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports, which can be additionally used, but should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== ==Software== 7bfc46869cb025037970ed74c355c19a2eb59b4a 325 324 2020-01-22T22:20:04Z Ziga 3 /* Power Controller and battery */ wikitext text/x-wiki __NOTOC__ [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. ==System on a Module (SOM)== This is the main system board, the computer. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports, which can be additionally used, but should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== ==Software== d65d411b7725b87bbe5d48bc133cb5923b00e1ce 326 325 2020-01-22T22:20:47Z Ziga 3 /* System on a Module (SOM) */ wikitext text/x-wiki __NOTOC__ [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. ==System on a Module (SOM)== This is the main system board, the computer. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports, which can be additionally used, but should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== ==Software== 9fcc86591f6cbbb3415cbac3e221167bf9dedbe7 327 326 2020-01-22T22:21:28Z Ziga 3 /* Software */ wikitext text/x-wiki __NOTOC__ [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. ==System on a Module (SOM)== This is the main system board, the computer. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports, which can be additionally used, but should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== ==Software== Software depends on a System on a Module used. 5dc133b2ac8e6dc21ad032656684ad02e4ad582e 351 327 2020-01-23T14:05:43Z Ziga 3 wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. ==System on a Module (SOM)== This is the main system board, the computer. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports, which can be additionally used, but should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== ==Software== Software depends on a System on a Module used. abebd633fcad049b7ffcc8ecee80a1554dc64671 0 46 312 290 2019-12-23T00:06:03Z Ziga 3 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. 2afc707e6f235d28733d8de0a86c028fb64f7714 316 312 2020-01-22T09:36:41Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. 49b237f554ca0a5c89941dfc9309a3e1719484c1 328 316 2020-01-22T22:25:12Z Ziga 3 reorder new with new stuff at the top wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 7306c4a4d2629142d3ef6099565de43b8e4de1ab 6 56 317 2020-01-22T21:47:57Z Ziga 3 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 8 24 329 275 2020-01-22T22:26:25Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact * News * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES 8e799e0ea8b88f6bc59417b244e71e734fbb8425 330 329 2020-01-22T22:26:47Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact * News|News * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES ba6f5bc6fadbc27a886ba3736dd7d6141bc1e927 331 330 2020-01-22T22:26:58Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact * [[News]] * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES 60814acd0da0b637f1a49acbddfa626e05c24fe9 332 331 2020-01-22T22:27:20Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** News|News ** Contact|Contact * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES 9dd08330170e44c453d9fa3cd9c7ad378ccf7297 333 332 2020-01-22T22:27:46Z Ziga 3 wikitext text/x-wiki * About ** News|News ** Balthazar|Introduction ** Goals|Goals ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES 241fb91125feb0b15dfac960ca58e4283d359a1b 334 333 2020-01-22T22:27:59Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** News|News ** Goals|Goals ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES c5df7b5057d21ea75e482255dec4c85eef772f60 335 334 2020-01-22T22:28:28Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Specifications and features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** News|News ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES abbc5fcc2906a0e9e756ea2cc425c5d82f738a19 350 335 2020-01-23T14:04:41Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Features|Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** News|News ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES 2b494653f38f0f47d52ed101859755ab7849e4c8 352 350 2020-01-23T14:06:24Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Features|Features & Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** News|News ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact * Wiki ** Special:RecentChanges|Recent Changes ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES 84826f5ecd6f4eeec0aef18f7ae9ed8da59a0162 0 5 336 303 2020-01-22T22:29:03Z Ziga 3 wikitext text/x-wiki __NOTOC__ ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> [[Image:BalthazarSet G1 2.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]]   6bfb670bd7b698c4b3c4280d31bcef94008fc2f6 337 336 2020-01-23T09:13:21Z Admin 1 wikitext text/x-wiki __NOTOC__ ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> [[Image:BalthazarSet G1 2.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]],[[Keyboard]] and [[Power Supply]]. fff4e57b0fa952973e91de751f128fb3a6dc841a 338 337 2020-01-23T09:13:53Z Admin 1 wikitext text/x-wiki __NOTOC__ ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' (Arjen Kamphuis in xTED speech in Delft)<br> [[Image:BalthazarSet G1 2.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]] and [[Power Supply]]. 184a38e004e36c236624cf963b0ceaba7e1dfbaa 346 338 2020-01-23T13:29:16Z Ziga 3 wikitext text/x-wiki __NOTOC__ ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]] and [[Power Supply]]. fa9b0ce8df05103f170086f012cdcdbcdc5cb529 347 346 2020-01-23T14:03:45Z Ziga 3 wikitext text/x-wiki __NOTOC__ This page documents features from more user-centric point of view. For a more engineering point of view, see [[Specifications]]. ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]] and [[Power Supply]]. f6051bb135d032fa892e60ac51f0cfb74ce38f42 348 347 2020-01-23T14:04:11Z Ziga 3 Ziga moved page [[Specifications and features]] to [[Features]] wikitext text/x-wiki __NOTOC__ This page documents features from more user-centric point of view. For a more engineering point of view, see [[Specifications]]. ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]] and [[Power Supply]]. f6051bb135d032fa892e60ac51f0cfb74ce38f42 354 348 2020-01-24T14:04:29Z Admin 1 /* Additional adapter with an onboard */ wikitext text/x-wiki __NOTOC__ This page documents features from more user-centric point of view. For a more engineering point of view, see [[Specifications]]. ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard:== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]] and [[Power Supply]]. cf24e20c6f6b41c0745e440ec5843e0a72706c59 0 57 339 2020-01-23T09:21:33Z Admin 1 Created page with "== Schematics == We have an early Balthazar system scheme as a block diagram upon which we develop and prototype separate boards to an interchangable compliance. File:Bal..." wikitext text/x-wiki == Schematics == We have an early Balthazar system scheme as a block diagram upon which we develop and prototype separate boards to an interchangable compliance. [[File:BalthazarBlockDia122.svg|frameless]] 5cd549671c9edc9b9b15302904fb00a041bfedc2 355 339 2020-01-27T07:04:51Z Admin 1 wikitext text/x-wiki == Schematics == We have an early Balthazar system scheme as a block diagram upon which we develop and prototype separate boards to an interchangable compliance. [[File:BalthazarBlockDia122.svg|frameless]] Balthazar laptop as a box consisting of: mainboard + all the perifery needed that make up a complete laptop: display, audio, keyboard, mousepad, wireless, usb, hdmi... and additionally: a buffered gpio (general purpose in/out) connector (not that laptop usually needs it...). The technology used benefits from the current rapid mobile platform development – as do all open- source single-board computers: Raspberry Pi, Orange Pi 4 – and a bit more advanced Firefly- RK3399. They all use SOC (system on chip) as the miniaturized combination of cpu/gpu/etc. The laptop should however be a pushed-up version of these single board computers - but still a single board computer. One format of recent computers is also the mini-pc. They are usually based on intel or amd laptop computer processors. LattePanda seems to be on the side of single-board-computers but uses Intel processors. Prices are also pushed up. The interchangeable module should basically be the board itself, while the stable part should be the skeleton: a specifically designed housing with display, keyboard, audio, mousepad, power supply. To upgrade – one buys a new board and inserts it in the place of the old board. f17cb14e60df464bfbd63fbb2045443ca4c14b16 0 58 340 2020-01-23T10:15:34Z Admin 1 Created page with "== Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Ad..." wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/abstracthat/dactyl-manuform Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. 6a9e0f5143f9d27527eff0e2ee7d91ffb29ea496 345 340 2020-01-23T10:42:18Z Admin 1 wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/abstracthat/dactyl-manuform Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. PCB [[File:Pcb left.png |thumb|left]] [[File:Pcb right.png|thumb|right]] [[File:Dm keyboard left wire diagram.png|thumb|left]] [[File:Dm keyboard right wire diagram.png|thumb|right]] ee27b6fc552e45b7c483e5bb1c8ab7d9ed8202a2 6 59 341 2020-01-23T10:24:11Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 60 342 2020-01-23T10:25:06Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 61 343 2020-01-23T10:26:00Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 62 344 2020-01-23T10:26:42Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 63 349 2020-01-23T14:04:11Z Ziga 3 Ziga moved page [[Specifications and features]] to [[Features]] wikitext text/x-wiki #REDIRECT [[Features]] df69f67b97dceae85d47166f4d5938e26178b22e 0 64 353 2020-01-24T13:41:03Z Admin 1 Created page with "== Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable..." wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. 1211d04d778664ab0baa86a274b31f927186793e 356 353 2020-01-27T07:08:35Z Admin 1 wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Blocks Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. c92de2bec148e1abd271858be855f7914c330074 357 356 2020-01-27T07:40:21Z Admin 1 wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. c26631914e9e1bc4d30e560e2a950c83e52b1207 359 357 2020-01-27T07:46:52Z Admin 1 wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. [[File:Balt ps.png|thumb|center]] fd34af600237f344cd4b4b19367cad8e999e194e 6 65 358 2020-01-27T07:42:44Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 64 360 359 2020-01-27T07:49:24Z Admin 1 wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] 29dc6d86fac051574f5d77cc2ad10cb2d0ff27aa 362 360 2020-01-27T07:55:47Z Admin 1 wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Battery Power Management Scheme === [[File:Battery Management-sch.pdf|thumb|center]] 051a4f4cd3289021260d9759a535abca16fdfd58 366 362 2020-01-27T10:23:06Z Admin 1 wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Battery Power Management Scheme === [[File:Battery Management-sch.pdf|thumb|center]] === Other options === [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === [[File:Balt pinebookpro PSU.png|thumb|center]] 6f2c3b3c4a0c5a6388c9618b8d8845a89b9f90ae 367 366 2020-01-27T10:31:36Z Admin 1 /* Reference to a Pinebook Pro: */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Battery Power Management Scheme === [[File:Battery Management-sch.pdf|thumb|center]] === Other options === [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] e3eb74a4de984996008315fa978d201088b87bf0 368 367 2020-01-27T10:33:55Z Admin 1 /* Other options */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Battery Power Management Scheme === [[File:Battery Management-sch.pdf|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] a6488f01900441bf0f58e0e6dffbc5631feaf998 369 368 2020-01-27T10:44:32Z Admin 1 /* Battery Power Management Scheme */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] 61cf1947d511efec6514e34801c08d055d2f1351 389 369 2020-03-16T10:53:25Z Admin 1 wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic version 0.2 Bill of materials PCB ready for prototype 1ba2a4c5c743de079a6f2c2c5b5f52a4bcea40b9 407 389 2020-03-17T08:52:21Z Admin 1 /* New PCB module for Balthazar has been developed. */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === [[File:Pcb-psu-proto06.png|thumb|left]] [[File:Pcb-psu-proto05.png|thumb|left]] Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic: [[File:BathazarPSU-Schematic03.pdf|thumb|left]] Bill of materials: [[File:BalthazarPSU-Bill.ods|thumb|left]] PCB ready for prototype. [[File:Pcb-psu-proto07.png|thumb|left]] [[File:Pcb-psu-proto04.png|thumb|left]] 0057c3b2ed4f0a2bb0994bc1225541fb653e018c 6 66 361 2020-01-27T07:52:05Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 67 363 2020-01-27T10:15:30Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 68 364 2020-01-27T10:18:04Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 69 365 2020-01-27T10:21:14Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 55 370 351 2020-01-27T16:53:14Z Admin 1 /* System on a Module (SOM) */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. ==System on a Module (SoM)== This is the main system board, the computer. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports, which can be additionally used, but should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== ==Software== Software depends on a System on a Module used. 592b48b611e2c1c792b2f874bf9a7b0e6417200e 371 370 2020-01-27T16:54:09Z Admin 1 /* Power Controller and battery */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, the computer. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports, which can be additionally used, but should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== ==Software== Software depends on a System on a Module used. 83eeab7957bbac8047c799a1abc63aa7c0945723 372 371 2020-01-27T16:55:51Z Admin 1 /* System on a Module (SoM) */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and good power supply. Often SOMs already provide a number of USB ports, which can be additionally used, but should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== ==Software== Software depends on a System on a Module used. 548d3e69dd7a425373ad17031ea26fae4f93eb79 373 372 2020-01-27T17:15:00Z Admin 1 /* USB hub */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and a good power supply. Often SOMs already provide a number of USB ports, which can be additionally used, but should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== ==Software== Software depends on a System on a Module used. 6812c08af06df9a6a3cd2269340688d83389c74d 374 373 2020-01-27T17:15:23Z Admin 1 /* USB hub */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and a good power supply. Often SoMs already provide a number of USB ports, which can be additionally used, but they should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== ==Software== Software depends on a System on a Module used. 031a76f17d9abb8a0de4599bb52e3717617f7e16 384 374 2020-03-05T14:30:18Z Ziga 3 /* Keyboard and Touch-pad */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and a good power supply. Often SoMs already provide a number of USB ports, which can be additionally used, but they should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. 2cee9e637bc776820fca9a0ee908b1b2cf38b38a 385 384 2020-03-05T14:30:48Z Ziga 3 /* System on a Module (SoM) */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[Sustem on a Module]] ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and a good power supply. Often SoMs already provide a number of USB ports, which can be additionally used, but they should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. 021ea1f9e96cc7293e6a67086eb83d46d821502c 386 385 2020-03-05T14:30:57Z Ziga 3 /* System on a Module (SoM) */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and a good power supply. Often SoMs already provide a number of USB ports, which can be additionally used, but they should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. ccd3adc88a5f8a9ddd6a4a0c0891793bc7ce6de6 0 37 375 313 2020-01-27T18:05:12Z Admin 1 /* Designs */ wikitext text/x-wiki __NOTOC__ ===News=== http://linuxgizmos.com/ ===Buyable Laptops=== https://www.pine64.org/pinebook-pro/ https://www.one-education.org/pages/infinity https://slimbook.es/en/ ===Designs=== https://sugarlabs.org/ https://mntmn.com/reform/ https://www.powerpc-notebook.org/en/ https://www.crowdsupply.com/sutajio-kosagi/novena ===Web Applications=== https://liveweave.com/ https://codesandbox.io/s/vanilla https://glitch.com/ e9872cde10a3d1b66118921645bc26adc5fbeea5 377 375 2020-01-30T07:46:32Z Admin 1 wikitext text/x-wiki __NOTOC__ ===News=== http://linuxgizmos.com/ ===Buyable Laptops=== https://www.pine64.org/pinebook-pro/ https://www.one-education.org/pages/infinity https://slimbook.es/en/ ===Designs=== https://sugarlabs.org/ https://mntmn.com/reform/ https://www.powerpc-notebook.org/en/ https://www.crowdsupply.com/sutajio-kosagi/novena ===Web Applications=== https://liveweave.com/ https://codesandbox.io/s/vanilla https://glitch.com/ ===Study and read=== http://laptopstudy.net/ b3cf4980f8bc6359b60996a4cd22309f487b3455 0 46 376 328 2020-01-30T07:40:01Z Admin 1 /* January 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. b71b0742667b06c24fafdc30b1a8517a6700309b 390 376 2020-03-16T11:15:21Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==March 2020== Two PCBs are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files real soon. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 93509682d6359b32de148fe23a2f7ebb2e4aecd6 0 58 378 345 2020-01-31T06:28:32Z Admin 1 wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. PCB [[File:Pcb left.png |thumb|left]] [[File:Pcb right.png|thumb|right]] [[File:Dm keyboard left wire diagram.png|thumb|left]] [[File:Dm keyboard right wire diagram.png|thumb|right]] 4ddee8932190a1eb985042b46fb7f767e7fa4c22 391 378 2020-03-16T13:25:12Z Admin 1 wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === [[File:Pcb left.png |thumb|center]] [[File:Pcb right.png|thumb|center]] [[File:Dm keyboard left wire diagram.png|thumb|center]] [[File:Dm keyboard right wire diagram.png|thumb|center]] === New keyboard PCB has been developed and adopted to a Balthazar dimensions === Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Bathazar keyboard schematic version 0.2 Bill of materials PCB ready for prototyping 474a5fea4862a4a08def39a210ddf58630cb0b65 393 391 2020-03-16T13:46:57Z Admin 1 /* New keyboard PCB has been developed and adopted to a Balthazar dimensions */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === [[File:Pcb left.png |thumb|center]] [[File:Pcb right.png|thumb|center]] [[File:Dm keyboard left wire diagram.png|thumb|center]] [[File:Dm keyboard right wire diagram.png|thumb|center]] === New keyboard PCB has been developed and adopted to a Balthazar dimensions === Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Balthazar keyboard schematic version 0.2 [[File:BalthazarKeyboardSchematic02.pdf|frameless|left]] Bill of materials PCB ready for prototyping dd00c69bb70d307b8e3327bd62a8e66bee9b7677 400 393 2020-03-17T08:38:46Z Admin 1 /* New keyboard PCB has been developed and adopted to a Balthazar dimensions */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === [[File:Pcb left.png |thumb|center]] [[File:Pcb right.png|thumb|center]] [[File:Dm keyboard left wire diagram.png|thumb|center]] [[File:Dm keyboard right wire diagram.png|thumb|center]] === New keyboard PCB has been developed and adopted to a Balthazar dimensions === [[File:Pcb-keyboard-proto05.png|thumb|left]] [[File:Pcb-keyboard-proto06.png|thumb|left]] Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping. [[File:Pcb-keyboard-proto03.png|thumb|left]] [[File:Pcb-keyboard-proto07.png|thumb|left]] [[File:Pcb-keyboard-proto04.png|thumb|left]] f22051f3e73beba36f44c3ed352b5a0b4e3e7717 408 400 2020-03-17T08:54:03Z Admin 1 /* Dev PCB */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === [[File:Pcb left.png |thumb|left]] [[File:Pcb right.png|thumb|left]] [[File:Dm keyboard left wire diagram.png|thumb|left]] [[File:Dm keyboard right wire diagram.png|thumb|left]] === New keyboard PCB has been developed and adopted to a Balthazar dimensions === [[File:Pcb-keyboard-proto05.png|thumb|left]] [[File:Pcb-keyboard-proto06.png|thumb|left]] Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping. [[File:Pcb-keyboard-proto03.png|thumb|left]] [[File:Pcb-keyboard-proto07.png|thumb|left]] [[File:Pcb-keyboard-proto04.png|thumb|left]] 9be2110cbfa2cb79d208d69bc17b8b5fb13a84e4 409 408 2020-03-17T08:54:47Z Admin 1 /* Dev PCB */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === [[File:Pcb left.png |thumb|center]] [[File:Pcb right.png|thumb|center]] [[File:Dm keyboard left wire diagram.png|thumb|center]] [[File:Dm keyboard right wire diagram.png|thumb|center]] === New keyboard PCB has been developed and adopted to a Balthazar dimensions === [[File:Pcb-keyboard-proto05.png|thumb|left]] [[File:Pcb-keyboard-proto06.png|thumb|left]] Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping. [[File:Pcb-keyboard-proto03.png|thumb|left]] [[File:Pcb-keyboard-proto07.png|thumb|left]] [[File:Pcb-keyboard-proto04.png|thumb|left]] f22051f3e73beba36f44c3ed352b5a0b4e3e7717 0 57 379 355 2020-02-19T15:51:57Z Admin 1 /* Schematics */ wikitext text/x-wiki == Schematics == We have an early Balthazar system scheme as a block diagram upon which we develop and prototype separate boards to an interchangable compliance. [[File:BalthazarBlockDia122.svg|frameless]] Balthazar laptop as a box consisting of: mainboard + all the perifery needed that make up a complete laptop: display, audio, keyboard, mousepad, wireless, usb, hdmi... and additionally: a buffered GPIO (general purpose in/out) connector (not that laptop usually needs it...). The technology used benefits from the current rapid mobile platform development – as do all open- source single-board computers:Banana Pi, Orange Pi 4 – and a bit more advanced Firefly- RK3399. They all use SOC (system on chip) as the miniaturized combination of CPU/GPU etc. The laptop should however be a pushed-up version of these single board computers - but still a single board computer. One format of recent computers is also the mini-pc. They are usually based on Intel or AMD laptop computer processors. LattePanda seems to be on the side of single-board-computers but uses Intel processors. Prices are also pushed up. The interchangeable module should basically be the board itself, while the stable part should be the skeleton: a specifically designed housing with display, keyboard, audio, mousepad, power supply. To upgrade – one buys a new board and inserts it in the place of the old board. e76529efa53bc69b798f276e9709cc2fd53bd430 381 379 2020-03-05T02:32:38Z Ziga 3 wikitext text/x-wiki == Schematics == We have an early Balthazar system scheme as a block diagram upon which we develop and prototype separate boards to an interchangable compliance. [[Image:BalthazarBlockDia122.svg]] Balthazar laptop as a box consisting of: mainboard + all the perifery needed that make up a complete laptop: display, audio, keyboard, mousepad, wireless, usb, hdmi... and additionally: a buffered GPIO (general purpose in/out) connector (not that laptop usually needs it...). The technology used benefits from the current rapid mobile platform development – as do all open- source single-board computers:Banana Pi, Orange Pi 4 – and a bit more advanced Firefly- RK3399. They all use SOC (system on chip) as the miniaturized combination of CPU/GPU etc. The laptop should however be a pushed-up version of these single board computers - but still a single board computer. One format of recent computers is also the mini-pc. They are usually based on Intel or AMD laptop computer processors. LattePanda seems to be on the side of single-board-computers but uses Intel processors. Prices are also pushed up. The interchangeable module should basically be the board itself, while the stable part should be the skeleton: a specifically designed housing with display, keyboard, audio, mousepad, power supply. To upgrade – one buys a new board and inserts it in the place of the old board. e27ce17dd63161f063d9c6121dd685b134de6326 382 381 2020-03-05T03:18:22Z Ziga 3 wikitext text/x-wiki == Schematics == We have an early Balthazar system scheme as a block diagram upon which we develop and prototype separate boards to an interchangable compliance. [[Image:BalthazarBlockDia122.svg]] Balthazar laptop as a box consisting of: mainboard + all the perifery needed that make up a complete laptop: display, audio, keyboard, mousepad, wireless, usb, hdmi... and additionally: a buffered GPIO (general purpose in/out) connector (not that laptop usually needs it...). The technology used benefits from the current rapid mobile platform development – as do all open- source single-board computers:Banana Pi, Orange Pi 4 – and a bit more advanced Firefly- RK3399. They all use SOC (system on chip) as the miniaturized combination of CPU/GPU etc. The laptop should however be a pushed-up version of these single board computers - but still a single board computer. One format of recent computers is also the mini-pc. They are usually based on Intel or AMD laptop computer processors. LattePanda seems to be on the side of single-board-computers but uses Intel processors. Prices are also pushed up. The interchangeable module should basically be the board itself, while the stable part should be the skeleton: a specifically designed housing with display, keyboard, audio, mousepad, power supply. To upgrade – one buys a new board and inserts it in the place of the old board. 6cfcb19b502a9e948bd3cf625bf630938a547390 8 24 380 352 2020-03-04T23:27:59Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Features|Features & Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** News|News ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact * Wiki ** Special:RecentChanges|Recent Changes ** Special:AllPages|All Pages ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES 540dec52863c985a78ba6eff39ec7a90b364fc99 0 35 383 260 2020-03-05T14:26:34Z Ziga 3 wikitext text/x-wiki ===Who is this for?=== Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its own data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and are able to use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also such institutions can make wide and creative use of a device’s on-board connections versatility and connectivity. Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [[Aperture Operating Environment]].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, educational community should find the value in overall physical sturdiness, software and a hardware sustainability of a '''BPCD'''. === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customised" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big budgeted large institution. ===But we have already have inexpensive netbooks, picturebooks, tablets, Chromebooks and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however they are locked in a certain software and hardware ecosystems and actually offer not too many security features. Also those devices do not work without the internet, so the reputation of such devices is often seen as a "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in a voluntary dissemination of their private data all over the internet, often being used as a bait for large companies that take an advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behavior. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have system invaded or spied on by any 3<small>rd</small> party. === What do you really want? === We want to enable and support low-income individuals and communities all over the planet with powerful, open and secure computing experience, while carefully partnering with “humaine” and ethical corporations along the way. Those will participate as a co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Or, alternatively they can build their own curriculum around '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education''', educational institutions, various charities, foundations and '''EU''' initiatives, so we can only hope they can deliver expected behavior and a practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. === But... A ''"Cloud"'' is free, cool, useful and hype. === Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> === So, why should me or my children want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their personal data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in controlling, testing and programming sensors, actuators and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. 7615c0846c6638348a8685b482b1e6f64fb89e1a 4 12 387 223 2020-03-05T14:33:01Z Ziga 3 Ziga moved page [[Website Tasks]] to [[Balthazar:Website Tasks]] wikitext text/x-wiki * WE NEED MAIL ADDRESSES. info,hw, sw -> @balthazar.space, -> ziga@balthazar.space, harv@balthazar.space, gizmo@balthazar.space * Menu bar * Remove unnecessary stuff from side menu ✔️ * Mobile CSS ✔️ * Color schema - distribute colors according to the 60-30-10 rule * Footer - missing stuff: transparency, financial report, who?, join us etc. in no particular order * URL rewriting ✔️ * Move search bar or incorporate it in the menu bar ✔️ * enable media gallery - tweak display and image viewing 3D and such * remove unused pages, images - clean means lean * better logo * links - cool stuff ✔️ * partners? ecosystem? e381ef95906798c8f833386e1f594e85e744ba5e 0 70 388 2020-03-05T14:33:01Z Ziga 3 Ziga moved page [[Website Tasks]] to [[Balthazar:Website Tasks]] wikitext text/x-wiki #REDIRECT [[Balthazar:Website Tasks]] 6e2daa437cbcf4d14f7496402622e6696dc2dca5 6 71 392 2020-03-16T13:42:24Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 72 394 2020-03-17T08:23:31Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 73 395 2020-03-17T08:26:22Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 74 396 2020-03-17T08:28:04Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 75 397 2020-03-17T08:31:37Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 76 398 2020-03-17T08:32:26Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 77 399 2020-03-17T08:33:11Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 78 401 2020-03-17T08:40:50Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 79 402 2020-03-17T08:43:48Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 80 403 2020-03-17T08:45:25Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 81 404 2020-03-17T08:47:08Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 82 405 2020-03-17T08:48:41Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 83 406 2020-03-17T08:51:09Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 64 410 407 2020-03-17T09:49:59Z Admin 1 /* New PCB module for Balthazar has been developed. */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilised sources. [[File:Pcb-psu-proto06.png|thumb|left]] [[File:Pcb-psu-proto05.png|thumb|left]] Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic: [[File:BathazarPSU-Schematic03.pdf|thumb|left]] Bill of materials: [[File:BalthazarPSU-Bill.ods|thumb|left]] PCB ready for prototype. [[File:Pcb-psu-proto07.png|thumb|left]] [[File:Pcb-psu-proto04.png|thumb|left]] 482956dbf2e5ec0d211d6a779babdd01c90f2f9b 417 410 2020-04-08T14:20:02Z Admin 1 wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilised sources. [[File:Pcb-psu-proto06.png|thumb|left]] [[File:Pcb-psu-proto05.png|thumb|left]] Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic: [[File:BathazarPSU-Schematic03.pdf|thumb|left]] Bill of materials: [[File:BalthazarPSU-Bill.ods|thumb|left]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space/balhazar Github] pages. [[File:Pcb-psu-proto07.png|thumb|left]] [[File:Pcb-psu-proto04.png|thumb|left]] 565a1d97f025a8f983cc2b349b75b7e471b3a400 6 84 411 2020-03-17T10:39:53Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 57 412 382 2020-03-17T10:41:42Z Admin 1 /* Schematics */ wikitext text/x-wiki == Schematics == We have an early Balthazar system scheme as a block diagram upon which we develop and prototype separate boards to an interchangable compliance. [[Image:BalthazarBlockDia122.svg]] Balthazar laptop as a box consisting of: mainboard + all the perifery needed that make up a complete laptop: display, audio, keyboard, mousepad, wireless, usb, hdmi... and additionally: a buffered GPIO (general purpose in/out) connector (not that laptop usually needs it...). The technology used benefits from the current rapid mobile platform development – as do all open- source single-board computers:Banana Pi, Orange Pi 4 – and a bit more advanced Firefly- RK3399. They all use SOC (system on chip) as the miniaturized combination of CPU/GPU etc. The laptop should however be a pushed-up version of these single board computers - but still a single board computer. One format of recent computers is also the mini-pc. They are usually based on Intel or AMD laptop computer processors. LattePanda seems to be on the side of single-board-computers but uses Intel processors. Prices are also pushed up. The interchangeable module should basically be the board itself, while the stable part should be the skeleton: a specifically designed housing with display, keyboard, audio, touch-pad, power supply. To upgrade – one buys a new board and inserts it in the place of the old board. If the keyboard PCB is meant to act as the complete top cover then it's height is also defined by the LCD -> 180mm. The touch-pad module would fit above the keys (as was envisioned in the broad design considerations recently) – not as usual below the keys. The two loudspeakers go to the usual positions left and right – at the two top edges of the full-size keyboard pcb. In this way the acoustic horn effect will be at its best with LCD screen up. Ideas and some crude sketching of I/O boards and inner guts: [[File:Innerguts drawing.png|thumb|left]] The mechanical skeleton built in this manner needs additionally an USB hub board on the top right which also takes in all the necessary inner periphery (camera, keyboard). There are some of these hubs on the market, but could be made here additionally. On to four hub is prefectly ok - two externally accessed USB-connectors and two internally used for camera, keyboard. The keyboard in this rudimentary fashion acting as the top is also very thin – maybe defining the triangle-like side cross-section – since there must be enough space at the top/ back/ bottom of the lower segment. The battery pack consisting of LiIo batteries are standardized in diameter – so this defines the height. About the same size are the vertically positioned USB-A female plugs. The loudpeaker sound greatly benefits from this volume behind. Let's repeat: the interchangeable CPU/ GPU upgrade module would basically be the mini-computer mainboard itself. To upgrade – one buys a new board and inserts it in the place of the old board. If the software and file system could be kept on some SSD version of mass storage – this would be an advantage (or maybe a necessity...). ff6b15c639120bda1f319c5237594aea44a08300 413 412 2020-03-17T10:51:09Z Admin 1 /* Schematics */ wikitext text/x-wiki == Schematics == We have an early Balthazar system scheme as a block diagram upon which we develop and prototype separate boards to an interchangable compliance. [[Image:BalthazarBlockDia122.svg]] Balthazar laptop as a box consisting of: mainboard + all the perifery needed that make up a complete laptop: display, audio, keyboard, mousepad, wireless, usb, hdmi... and additionally: a buffered GPIO (general purpose in/out) connector (not that laptop usually needs it...). The technology used benefits from the current rapid mobile platform development – as do all open- source single-board computers:Banana Pi, Orange Pi 4 – and a bit more advanced Firefly- RK3399. They all use SOC (system on chip) as the miniaturized combination of CPU/GPU etc. The laptop should however be a pushed-up version of these single board computers - but still a single board computer. One format of recent computers is also the mini-pc. They are usually based on Intel or AMD laptop computer processors. LattePanda seems to be on the side of single-board-computers but uses Intel processors. Prices are also pushed up. The interchangeable module should basically be the board itself, while the stable part should be the skeleton: a specifically designed housing with display, keyboard, audio, touch-pad, power supply. To upgrade – one buys a new board and inserts it in the place of the old board. If the keyboard PCB is meant to act as the complete top cover then it's height is also defined by the LCD -> 180mm. The touch-pad module would fit above the keys (as was envisioned in the broad design considerations recently) – not as usual below the keys. The two loudspeakers go to the usual positions left and right – at the two top edges of the full-size keyboard pcb. In this way the acoustic horn effect will be at its best with LCD screen up. Ideas and some crude sketching of I/O boards and inner guts: [[File:Innerguts drawing.png|thumb|center]] The mechanical skeleton built in this manner needs additionally an USB hub board on the top right which also takes in all the necessary inner periphery (camera, keyboard). There are some of these hubs on the market, but could be made here additionally. On to four hub is prefectly ok - two externally accessed USB-connectors and two internally used for camera, keyboard. The keyboard in this rudimentary fashion acting as the top is also very thin – maybe defining the triangle-like side cross-section – since there must be enough space at the top/ back/ bottom of the lower segment. The battery pack consisting of LiIo batteries are standardized in diameter – so this defines the height. About the same size are the vertically positioned USB-A female plugs. The loudpeaker sound greatly benefits from this volume behind. Let's repeat: the interchangeable CPU/ GPU upgrade module would basically be the mini-computer mainboard itself. To upgrade – one buys a new board and inserts it in the place of the old board. If the software and file system could be kept on some SSD version of mass storage – this would be an advantage (or maybe a necessity...). 91347a9e522daabe5a821c2056f435ad6d1fe826 8 24 414 380 2020-04-02T19:19:18Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Features|Features & Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** News|News ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact ** GitHub|GitHub * Wiki ** Special:RecentChanges|Recent Changes ** Special:AllPages|All Pages ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES 5b5aebd9e6bd63502eca8de213cdb19dcee3c717 415 414 2020-04-02T19:19:45Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Features|Features & Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** News|News ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact ** https://github.com|GitHub * Wiki ** Special:RecentChanges|Recent Changes ** Special:AllPages|All Pages ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES f0cb47f55394cf66ae3ca3be353a91fe5f677b30 416 415 2020-04-02T19:20:18Z Ziga 3 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Features|Features & Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** News|News ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact ** https://github.com/balthazar-space|GitHub page * Wiki ** Special:RecentChanges|Recent Changes ** Special:AllPages|All Pages ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES 383d20a707747589a108966b6520714d2c7b79e9 0 58 418 409 2020-04-08T14:20:50Z Admin 1 wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === [[File:Pcb left.png |thumb|center]] [[File:Pcb right.png|thumb|center]] [[File:Dm keyboard left wire diagram.png|thumb|center]] [[File:Dm keyboard right wire diagram.png|thumb|center]] === New keyboard PCB has been developed and adopted to a Balthazar dimensions === [[File:Pcb-keyboard-proto05.png|thumb|left]] [[File:Pcb-keyboard-proto06.png|thumb|left]] Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space/balhazar Github] pages. [[File:Pcb-keyboard-proto03.png|thumb|left]] [[File:Pcb-keyboard-proto07.png|thumb|left]] [[File:Pcb-keyboard-proto04.png|thumb|left]] fb1c4bb35684861a24d598f965e038be4102b491 0 46 419 390 2020-04-10T14:38:29Z Admin 1 /* March 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also opened a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 88b2d09d18607afcb83302792f9d18c978ec8da9 420 419 2020-04-10T14:45:15Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==April 2020== We have opened a Github page with KiCad files too ready for download. Also our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". THis month we will start to develop I/O board and work on some casing issues as well as our promised docking board for camera, microphone and USB security dongle port. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 4d514523a7cda839f1bb7e419ff316e539110187 421 420 2020-04-10T14:48:20Z Admin 1 /* April 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==April 2020== It has been a one year that our idea has been born. We have opened a Github page with KiCad files too ready for download. Also our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". THis month we will start to develop I/O board and work on some casing issues as well as our promised docking board for camera, microphone and USB security dongle port. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 5c20356e68002fa3a652ccffba3aecbbbefc55fc 422 421 2020-04-10T17:35:49Z Ziga 3 /* April 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==April 2020== It has been a one year that our idea has been born. We have opened a Github page with KiCad files ready for download. Also our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". THis month we will start to develop I/O board and work on some casing issues as well as our promised docking board for camera, microphone and USB security dongle port. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 8170e3fb50b66c18e3f34358868ab0330e6b7a94 423 422 2020-04-10T17:36:05Z Ziga 3 /* April 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==April 2020== It has been a one year that our idea has been born. We have opened a Github page with KiCad files ready to download. Also our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". THis month we will start to develop I/O board and work on some casing issues as well as our promised docking board for camera, microphone and USB security dongle port. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 8767e88978de1908561b91f09c8d47461b23f7ac 424 423 2020-04-10T17:36:57Z Ziga 3 /* April 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==April 2020== It has been a one year that our idea has been born. We have opened a Github page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". This month we will start to develop I/O board and work on some casing issues as well as our promised docking board for camera, microphone and USB security dongle port. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 34bfc9e5c45c961b176e14e6d5064fc11e8db8a9 426 424 2020-05-05T08:07:29Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==May 2020== May has started with drawing the designs for I/O hub or a board that will enable a connect to our keyboard and power supply. We are aiming for the publishing our preliminary designs in and around mid-May. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". This month we will start to develop I/O board and work on some casing issues as well as our promised docking board for camera, microphone and USB security dongle port. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. c3175aae8ed32a4b0738db8544b9b4c655bff0c2 427 426 2020-05-05T08:19:13Z Admin 1 /* May 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==May 2020== May has started with drawing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. We are aiming for the publishing our preliminary designs in and around mid-May. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". This month we will start to develop I/O board and work on some casing issues as well as our promised docking board for camera, microphone and USB security dongle port. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 45179e2492caeb4b924fd8cf0305d7a86a065211 456 427 2020-05-18T09:26:12Z Admin 1 /* May 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". This month we will start to develop I/O board and work on some casing issues as well as our promised docking board for camera, microphone and USB security dongle port. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 2a4d1ec3b6e40837cf97f64068d8a8e962073b24 457 456 2020-05-18T09:30:47Z Admin 1 /* April 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files forour internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. a8f0cb5e9d34b21fe5e8923b6c0bc7077f896846 458 457 2020-05-18T11:37:04Z Admin 1 /* April 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. ba8c152fbdfb8a93e805f2cf5a58ef92a0477522 0 1 425 285 2020-04-21T16:23:08Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <br> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[News|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. Also, check out our [https://github.com/balthazar-space GitHub pages]. 997141b37efec782e1ac40b4d0e606826711e780 430 425 2020-05-05T17:45:23Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <div style="background: #ffd; margin: auto;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]], [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] </div> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[News|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. Also, check out our [https://github.com/balthazar-space GitHub pages]. 9ae0911fc0ce78f7a02c5d6023cdd8f73d115c01 431 430 2020-05-05T17:47:08Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <div style="background: #ffd; margin: auto; font-size: 144%;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]], [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] </div> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[News|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. Also, check out our [https://github.com/balthazar-space GitHub pages]. 3cd1babd4be5c861b8b5a1d893e08b24eadc7ab6 432 431 2020-05-05T17:54:53Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <div style="background: #ffd; margin: auto; font-size: 144%;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]], [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] * List all [[Special:ListFiles|Files]] or [[Special:AllPages|Pages]] </div> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[News|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. Also, check out our [https://github.com/balthazar-space GitHub pages]. 313537411c1c247fd903cbc003e9f867abcfda26 433 432 2020-05-05T17:57:10Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <div style="background: #ffd; margin: auto; font-size: 144%; column-count: 2;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]], [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] * List all [[Special:ListFiles|Files]] or [[Special:AllPages|Pages]] </div> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[News|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. Also, check out our [https://github.com/balthazar-space GitHub pages]. 416afee21da8b1c43a06aa302e6a5678a61dbcec 434 433 2020-05-05T17:59:56Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === <div style="background: #ffd; margin: auto; font-size: 144%; column-count: 2;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]], [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] * List all [[Special:ListFiles|Files]] or [[Special:AllPages|Pages]] </div> ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[News|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. Also, check out our [https://github.com/balthazar-space GitHub pages]. 9ad8a2723c979664a94e9e0f8c44e5d2debb1ad4 437 434 2020-05-05T21:28:46Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === <div style="background: #ffd; margin: auto; font-size: 144%; column-count: 2;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] * List all [[Special:ListFiles|Files]] or [[Special:AllPages|Pages]] </div> ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[News|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. Also, check out our [https://github.com/balthazar-space GitHub pages]. 01494d78c377744f888adcfc3ab214f36056f99b 438 437 2020-05-05T21:31:51Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === <div style="background: #ffd; margin: auto; font-size: 144%; column-count: 2;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] * [[Special:ListFiles|List files]] * [[Special:AllPages|All pages]] </div> ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[News|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. Also, check out our [https://github.com/balthazar-space GitHub pages]. 929ede29937c0ecd44644521def794aaad88b353 439 438 2020-05-05T21:34:37Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === <div style="background: #ffd; margin: auto; font-size: 144%; column-count: 2;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] * [[Special:ListFiles|List files]] and [[Special:AllPages|All pages]] </div> ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[News|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. Also, check out our [https://github.com/balthazar-space GitHub pages]. 74e8c437a3dcf0ea4c518b0a274ac1b3985d418e 440 439 2020-05-06T07:40:29Z Admin 1 /* One laptop for the new internet. */ wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== <div style="background: #ffd; margin: auto; font-size: 120%; column-count: 2;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] * [[Special:ListFiles|List files]] and [[Special:AllPages|All pages]] </div> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''OSHW''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> Please read the [[Goals|'''Goals''']], [[FAQ|'''Frequently asked questions''']], [[News|'''Actual''']] and the [[Specifications and features|'''Specifications and features''']]. Also, check out our [https://github.com/balthazar-space GitHub pages]. 675107749ea467fe6cb4d22cea0b03e4fe92062f 441 440 2020-05-06T09:12:00Z Admin 1 /* Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. */ wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == === One laptop for the new internet. === ==== Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that. ==== [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #ffa; margin: auto; font-size: 80%; column-count: 3;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] </div> 507f13075e6d0ea5f27b0a37f53ac4a01af1f421 442 441 2020-05-06T09:15:55Z Admin 1 /* One laptop for the new internet. */ wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #ffa; margin: auto; font-size: 80%; column-count: 3;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] </div> d7a9c88452762ab5e1f4872f36bbf8b222e81971 443 442 2020-05-06T09:17:19Z Admin 1 /* a Personal Computing Device */ wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #ffa; margin: auto; font-size: 80%; column-count: 3;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] </div> afe5a80d925c718252c6c73770896c16e811ac6d 444 443 2020-05-06T14:46:10Z Admin 1 /* a Personal Computing Device */ wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #ffc; margin: auto; font-size: 80%; column-count: 3;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact]] * [https://github.com/balthazar-space GitHub pages] </div> 8439a7a1911ac0543051f6653f602be8155cbdbb 445 444 2020-05-09T20:42:20Z Ziga 3 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #ffc; margin: auto; font-size: 80%; column-count: 3;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> f8e463fecee50d44cd0a7810c9e3c690c1ef0b08 4 3 428 8 2020-05-05T08:30:51Z Admin 1 wikitext text/x-wiki Balthazar is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN OSHL and GNU-GPL compliant FOSS laptop as a personal computing device. PCD will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. Consortium consists of an industry and academia personas and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage FOSS software developers to create a secure, easy to use and intuitive user-friendly software and apps for the Balthazar Personal Computing Device. da558cb79632797c9650212731b599add6af7659 429 428 2020-05-05T08:33:28Z Admin 1 wikitext text/x-wiki Balthazar is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. PCD will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. Consortium consists of an industry and academia personas and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage FOSS software developers to create a secure, easy to use and intuitive user-friendly software and apps for the Balthazar Personal Computing Device. 9ec4d727e76fbd75539d2d80ef60d9396f740d59 0 55 435 386 2020-05-05T18:01:21Z Ziga 3 wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and a good power supply. Often SoMs already provide a number of USB ports, which can be additionally used, but they should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 7b35e0bab6a81d0120921e3043d71631c695ddf4 436 435 2020-05-05T18:01:35Z Ziga 3 wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==USB hub== Provides the main infrastructure for connecting peripherals. Need to have many ports and a good power supply. Often SoMs already provide a number of USB ports, which can be additionally used, but they should not be required. At least USB 2 or better. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] ddbcbc0a24c8481ccaf738cdf4b568f7c769d56f 446 436 2020-05-18T06:12:42Z Admin 1 /* USB hub */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==USB hub== Internal usb devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external usb devices disabling the usb power line is the same as unplugging the usb device. The condom approach with disabling the data lines is a bit better, but solves things mostly with usb plugging into public charging stations. The TPS2540 solution above is usb charging current negotiator – with no datalines connected. A dedicated (micro-usb) charging port solves this problem. The already developed Balthazar PSU-charger has this option. The job of preventing uncontrolled usb traffic from the external peripheral device which runs its own software system is problematic and should probably be done on the level of usb driver. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 11f40b5b73c91a5f7d371519924107d51953b36a 447 446 2020-05-18T06:16:01Z Admin 1 /* USB hub */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Display Controller and panel== Provides interface to display panel by HDMI ==Case== ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 8e30c94639f19209a64229b2c3d4c5139a511cdb 0 85 448 2020-05-18T06:21:56Z Admin 1 Created page with "==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard +..." wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple usb 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster usb port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the usb power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. The job of preventing uncontrolled USB traffic from the external peripheral device which runs its own software system is problematic and should probably be done on the level of USB driver. fe82904c6717f36e56e27189074c29c0ec5d2f50 450 448 2020-05-18T06:25:45Z Admin 1 wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple usb 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster usb port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual usb high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal usb periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the usb power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. The job of preventing uncontrolled USB traffic from the external peripheral device which runs its own software system is problematic and should probably be done on the level of USB driver. dbb55f92ee7360473db4f3f8c5b8b9370e2742f1 454 450 2020-05-18T06:52:22Z Admin 1 wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple usb 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster usb port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual usb high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal usb periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. [[File:BalthazarIOusb 0.png|thumb|center]] [[File:BalthazarIOusb 2.png|thumb|center]] [[File:BalthazarIOusb 1.png|thumb|center]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space/balhazar Github] pages. 8e5d4e1ae6fffb41d009e80d1b0a42fa93435810 455 454 2020-05-18T07:32:32Z Admin 1 /* Balthazar I/O USB board */ wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple USB 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster USB port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. [[File:BalthazarIOusb 0.png|thumb|center]] [[File:BalthazarIOusb 2.png|thumb|center]] [[File:BalthazarIOusb 1.png|thumb|center]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space/balhazar Github] pages. 02d9e5e2f82505f68704e008bbc8942dd40f4a16 459 455 2020-05-19T16:31:23Z Admin 1 /* Balthazar I/O USB board */ wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple USB 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster USB port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. [[File:BalthazarIOusb 0.png|thumb|center]] [[File:BalthazarIOusb 2.png|thumb|center]] [[File:BalthazarIOusb 1.png|thumb|center]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. ad70ab60bf63a95738b992e65825eb3b067e9fd8 6 86 449 2020-05-18T06:24:54Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 87 451 2020-05-18T06:49:11Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 88 452 2020-05-18T06:50:07Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 89 453 2020-05-18T06:51:03Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 58 460 418 2020-05-19T16:32:43Z Admin 1 /* New keyboard PCB has been developed and adopted to a Balthazar dimensions */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === [[File:Pcb left.png |thumb|center]] [[File:Pcb right.png|thumb|center]] [[File:Dm keyboard left wire diagram.png|thumb|center]] [[File:Dm keyboard right wire diagram.png|thumb|center]] === New keyboard PCB has been developed and adopted to a Balthazar dimensions === [[File:Pcb-keyboard-proto05.png|thumb|left]] [[File:Pcb-keyboard-proto06.png|thumb|left]] Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. [[File:Pcb-keyboard-proto03.png|thumb|left]] [[File:Pcb-keyboard-proto07.png|thumb|left]] [[File:Pcb-keyboard-proto04.png|thumb|left]] be7fc60db6548909fcae0b755458f5c08048b445 465 460 2020-05-24T10:35:49Z Admin 1 /* New keyboard PCB has been developed and adopted to a Balthazar dimensions */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === [[File:Pcb left.png |thumb|center]] [[File:Pcb right.png|thumb|center]] [[File:Dm keyboard left wire diagram.png|thumb|center]] [[File:Dm keyboard right wire diagram.png|thumb|center]] === New keyboard PCB has been developed and adopted to a Balthazar dimensions === [[File:Pcb-keyboard-proto05.png|thumb|left]] [[File:Pcb-keyboard-proto06.png|thumb|left]] Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. [[File:Pcb-keyboard-proto03.png|thumb|left]] [[File:Pcb-keyboard-proto07.png|thumb|left]] [[File:Pcb-keyboard-proto04.png|thumb|left]] ac663fe91ab6a6952f9eb554f8399e85cc8ccdc5 483 465 2020-11-11T11:26:52Z Admin 1 /* New keyboard PCB has been developed and adopted to a Balthazar dimensions */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === [[File:Pcb left.png |thumb|center]] [[File:Pcb right.png|thumb|center]] [[File:Dm keyboard left wire diagram.png|thumb|center]] [[File:Dm keyboard right wire diagram.png|thumb|center]] === New keyboard PCB has been developed and adopted to a Balthazar dimensions === [[File:Pcb-keyboard-proto05.png|thumb|left]] [[File:Pcb-keyboard-proto06.png|thumb|left]] Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. [[Gallery |title=Keyboard views |width=160 | height=170 |align=center |footer=Keyboard|File:Pcb-keyboard-proto03.png|thumb]] [[File:Pcb-keyboard-proto07.png|thumb]] [[File:Pcb-keyboard-proto04.png|thumb]] === Prototype PCB === In early November 2020 we have received first prototypes of a keyboard PCBs ready for implementing and for the correct dimensioning of a case and a screen. Here are the photos of a prototype, also with a 13.3" screen. [[File:Key schem.png|thumb|left]] [[File:Key scr1.png|thumb|center]] [[File:Key balt2cl.png|thumb|right]] 55775db9d675169c19caa821c9cd0dfa2c7a712e 484 483 2020-11-11T11:42:03Z Admin 1 /* New keyboard PCB has been developed and adopted to a Balthazar dimensions */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === [[File:Pcb left.png |thumb|center]] [[File:Pcb right.png|thumb|center]] [[File:Dm keyboard left wire diagram.png|thumb|center]] [[File:Dm keyboard right wire diagram.png|thumb|center]] === New keyboard PCB has been developed and adopted to a Balthazar dimensions === [[File:Pcb-keyboard-proto05.png|thumb|left]] [[File:Pcb-keyboard-proto06.png|thumb|left]] Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020 we have received first prototypes of a keyboard PCBs ready for implementing and for the correct dimensioning of a case and a screen. Here are the photos of a prototype, also with a 13.3" screen. [[File:Key schem.png|thumb|left]] [[File:Key scr1.png|thumb|center]] [[File:Key balt2cl.png|thumb|right]] 8477cf47329e48a6b56dd7d79ba03c3c501da63c 485 484 2020-11-11T11:44:44Z Admin 1 /* Prototype PCB */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === [[File:Pcb left.png |thumb|center]] [[File:Pcb right.png|thumb|center]] [[File:Dm keyboard left wire diagram.png|thumb|center]] [[File:Dm keyboard right wire diagram.png|thumb|center]] === New keyboard PCB has been developed and adopted to a Balthazar dimensions === [[File:Pcb-keyboard-proto05.png|thumb|left]] [[File:Pcb-keyboard-proto06.png|thumb|left]] Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020 we have received first prototypes of a keyboard PCBs ready for implementing and for the correct dimensioning of a case and a screen. Here are the photos of a prototype, also with a 13.3" screen. <gallery> File:Key schem.png|thumb|with schematic File:Key scr1.png|thumb|with the screen File:Key balt2cl.png|thumb|close-up </gallery> 9acd4a76981b245db559e46644c0573763447d82 486 485 2020-11-11T11:50:03Z Admin 1 /* Keyboard */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === <gallery> File:Pcb left.png |thumb| File:Pcb right.png|thumb| File:Dm keyboard left wire diagram.png|thumb| File:Dm keyboard right wire diagram.png|thumb| </gallery> === New keyboard PCB has been developed and adopted to a Balthazar dimensions === <gallery> File:Pcb-keyboard-proto05.png|thumb|top File:Pcb-keyboard-proto06.png|thumb|bottom </gallery> Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020 we have received first prototypes of a keyboard PCBs ready for implementing and for the correct dimensioning of a case and a screen. Here are the photos of a prototype, also with a 13.3" screen. <gallery> File:Key schem.png|thumb|with schematic File:Key scr1.png|thumb|with the screen File:Key balt2cl.png|thumb|close-up </gallery> 0c06c4d712f940a68ddc9068a1e331b6aa61f8ef 487 486 2020-11-11T11:52:32Z Admin 1 /* Prototype PCB */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === <gallery> File:Pcb left.png |thumb| File:Pcb right.png|thumb| File:Dm keyboard left wire diagram.png|thumb| File:Dm keyboard right wire diagram.png|thumb| </gallery> === New keyboard PCB has been developed and adopted to a Balthazar dimensions === <gallery> File:Pcb-keyboard-proto05.png|thumb|top File:Pcb-keyboard-proto06.png|thumb|bottom </gallery> Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020 we have received first prototypes of a keyboard PCBs ready for implementing and for the correct dimensioning of a case and adjoining the screen. Here are the photos of a prototype, also with a 13.3" screen. <gallery> File:Key schem.png|thumb|with the schematic File:Key scr1.png|thumb|with the screen File:Key balt2cl.png|thumb|close-up </gallery> f49914ac6406f667816af483a62a9ea6f76c3e41 492 487 2020-11-17T08:41:06Z Admin 1 /* Prototype PCB */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === <gallery> File:Pcb left.png |thumb| File:Pcb right.png|thumb| File:Dm keyboard left wire diagram.png|thumb| File:Dm keyboard right wire diagram.png|thumb| </gallery> === New keyboard PCB has been developed and adopted to a Balthazar dimensions === <gallery> File:Pcb-keyboard-proto05.png|thumb|top File:Pcb-keyboard-proto06.png|thumb|bottom </gallery> Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[File:BalthazarKeyboardSchematic02.pdf|thumb|left]] Bill of materials: [[File:BalthazarKeyboard-Bill.ods|thumb|left]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020 we have received first prototypes of a keyboard PCBs, ready for implementing and connecting it to the other modules and for the correct dimensioning of a case and adjoining the screen. Here are the photos of a prototype, also with a 13.3" screen. <gallery> File:Key schem.png|thumb|with the schematic File:Key scr1.png|thumb|with the screen File:Key balt2cl.png|thumb|close-up </gallery> 17510d81880e0c9f2468612b58d29a974264da2f 493 492 2020-11-17T08:57:39Z Admin 1 /* New keyboard PCB has been developed and adopted to a Balthazar dimensions */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === <gallery> File:Pcb left.png |thumb| File:Pcb right.png|thumb| File:Dm keyboard left wire diagram.png|thumb| File:Dm keyboard right wire diagram.png|thumb| </gallery> === New keyboard PCB has been developed and adopted to a Balthazar dimensions === <gallery> File:Pcb-keyboard-proto05.png|thumb|top File:Pcb-keyboard-proto06.png|thumb|bottom </gallery> Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[:File:BalthazarKeyboardSchematic02.pdf|Keyboard Schematics]] Bill of materials: [[:File:BalthazarKeyboard-Bill.ods|B.O.M.]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020 we have received first prototypes of a keyboard PCBs, ready for implementing and connecting it to the other modules and for the correct dimensioning of a case and adjoining the screen. Here are the photos of a prototype, also with a 13.3" screen. <gallery> File:Key schem.png|thumb|with the schematic File:Key scr1.png|thumb|with the screen File:Key balt2cl.png|thumb|close-up </gallery> 533b55a0adaa3e8fdda7f85564bd0e37fea88a5b 494 493 2020-11-17T08:58:03Z Admin 1 /* Prototype PCB */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === <gallery> File:Pcb left.png |thumb| File:Pcb right.png|thumb| File:Dm keyboard left wire diagram.png|thumb| File:Dm keyboard right wire diagram.png|thumb| </gallery> === New keyboard PCB has been developed and adopted to a Balthazar dimensions === <gallery> File:Pcb-keyboard-proto05.png|thumb|top File:Pcb-keyboard-proto06.png|thumb|bottom </gallery> Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics: [[:File:BalthazarKeyboardSchematic02.pdf|Keyboard Schematics]] Bill of materials: [[:File:BalthazarKeyboard-Bill.ods|B.O.M.]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020 we have received first prototypes of a keyboard PCBs, ready for implementing and connecting it to the other modules and for the correct dimensioning of a case and adjoining the screen. Here are the photos of a prototype, also with a 13.3" screen. <gallery> File:Key schem.png|thumb|with the schematic File:Key scr1.png|thumb|with the screen File:Key balt2cl.png|thumb|close-up with logo </gallery> ab634b9a2a450cbbdbe212f544a14f207a87a30c 495 494 2020-11-17T09:08:28Z Admin 1 /* New keyboard PCB has been developed and adopted to a Balthazar dimensions */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === <gallery> File:Pcb left.png |thumb| File:Pcb right.png|thumb| File:Dm keyboard left wire diagram.png|thumb| File:Dm keyboard right wire diagram.png|thumb| </gallery> === New keyboard PCB has been developed and adopted to a Balthazar dimensions === <gallery> File:Pcb-keyboard-proto05.png|thumb|top File:Pcb-keyboard-proto06.png|thumb|bottom </gallery> Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics in: [[:File:BalthazarKeyboardSchematic02.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarKeyboard-Bill.ods|.ODS]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020 we have received first prototypes of a keyboard PCBs, ready for implementing and connecting it to the other modules and for the correct dimensioning of a case and adjoining the screen. Here are the photos of a prototype, also with a 13.3" screen. <gallery> File:Key schem.png|thumb|with the schematic File:Key scr1.png|thumb|with the screen File:Key balt2cl.png|thumb|close-up with logo </gallery> 98a87d31e04d642ca83446a2b4e1695debc1aa02 497 495 2020-11-17T11:10:11Z Admin 1 wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === <gallery> File:Pcb left.png |thumb| File:Pcb right.png|thumb| File:Dm keyboard left wire diagram.png|thumb| File:Dm keyboard right wire diagram.png|thumb| </gallery> === New keyboard PCB has been developed and adopted to a Balthazar dimensions === <gallery> File:Pcb-keyboard-proto05.png|thumb|top File:Pcb-keyboard-proto06.png|thumb|bottom </gallery> Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics in: [[:File:BalthazarKeyboardSchematic02.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarKeyboard-Bill.ods|.ODS]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020 we have received first prototypes of a keyboard PCBs, ready for implementing and connecting it to the other modules and for the correct dimensioning of a case and adjoining the screen. Here are the photos of a prototype, also with a 13.3" screen. <gallery> File:Key schem.png|thumb|with the schematic File:Key scr1.png|thumb|with the screen File:Key balt2cl.png|thumb|close-up with logo </gallery> Go to: [[I/O_USB|I/O hub]] or [[Power_Supply|Power Supply]] 5b06c6cd40d96432240323a70c473b12cc611f7a 506 497 2020-11-23T17:45:12Z Admin 1 /* Prototype PCB */ wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our developement by Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided in left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === <gallery> File:Pcb left.png |thumb| File:Pcb right.png|thumb| File:Dm keyboard left wire diagram.png|thumb| File:Dm keyboard right wire diagram.png|thumb| </gallery> === New keyboard PCB has been developed and adopted to a Balthazar dimensions === <gallery> File:Pcb-keyboard-proto05.png|thumb|top File:Pcb-keyboard-proto06.png|thumb|bottom </gallery> Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error there is a mechanical switch on PSU board to stop charging. In this way three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard pcb has some dimensions already defined by the LCD's dimensions of 13.3 inch in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low cost membrane switches. A little better solution are the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics in: [[:File:BalthazarKeyboardSchematic02.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarKeyboard-Bill.ods|.ODS]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020 we have received first prototypes of a keyboard PCBs, ready for implementing and connecting it to the other modules and for the correct dimensioning of a case and adjoining the screen. Here are the photos of a prototype, also with a 13.3" screen. <gallery> File:Key schem.png|thumb|with the schematic File:Key scr1.png|thumb|with the screen File:Key balt2cl.png|thumb|close-up with logo </gallery> Here it is with the key modules soldered on a keyboard prototype PCB, also with the controller chip and a micro USB. <gallery> File:Key solderedon.png|thumb|with the keys soldered on File:Key back.png|thumb|back side with a controller File:Keybackclup.png|thumb|controller close-up File:Key keyonclup.png|thumb|key modules close-up </gallery> Go to: [[I/O_USB|I/O hub]] or [[Power_Supply|Power Supply]] 69caba295e9aa1c939b53d3e7191f40231277db1 0 64 461 417 2020-05-19T16:34:18Z Admin 1 /* New PCB module for Balthazar has been developed. */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilised sources. [[File:Pcb-psu-proto06.png|thumb|left]] [[File:Pcb-psu-proto05.png|thumb|left]] Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic: [[File:BathazarPSU-Schematic03.pdf|thumb|left]] Bill of materials: [[File:BalthazarPSU-Bill.ods|thumb|left]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. [[File:Pcb-psu-proto07.png|thumb|left]] [[File:Pcb-psu-proto04.png|thumb|left]] d012eaeb633b6c6fe4c447dded6c5ec3ef30dd8d 466 461 2020-05-24T10:36:49Z Admin 1 /* New PCB module for Balthazar has been developed. */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilised sources. [[File:Pcb-psu-proto06.png|thumb|left]] [[File:Pcb-psu-proto05.png|thumb|left]] Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic: [[File:BathazarPSU-Schematic03.pdf|thumb|left]] Bill of materials: [[File:BalthazarPSU-Bill.ods|thumb|left]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. [[File:Pcb-psu-proto07.png|thumb|left]] [[File:Pcb-psu-proto04.png|thumb|left]] 3e06a643623fe35a58f1fda44ec1fb7c408638cf 489 466 2020-11-11T12:01:33Z Admin 1 /* New PCB module for Balthazar has been developed. */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilised sources. <gallery> File:Pcb-psu-proto06.png|thumb| File:Pcb-psu-proto05.png|thumb| File:Pcb-psu-proto07.png|thumb| File:Pcb-psu-proto04.png|thumb| </gallery> Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic: [[File:BathazarPSU-Schematic03.pdf|thumb|left]] Bill of materials: [[File:BalthazarPSU-Bill.ods|thumb|left]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. ae8f90c8976d1403447d8e9ad2b860f3f2eb53d5 496 489 2020-11-17T09:13:08Z Admin 1 /* New PCB module for Balthazar has been developed. */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilised sources. <gallery> File:Pcb-psu-proto06.png|thumb| File:Pcb-psu-proto05.png|thumb| File:Pcb-psu-proto07.png|thumb| File:Pcb-psu-proto04.png|thumb| </gallery> Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic in: [[:File:BathazarPSU-Schematic03.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarPSU-Bill.ods|.ODS]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. 0965789ad9bdc9c9ece677bc4eff01daa65f052d 499 496 2020-11-17T11:13:36Z Admin 1 wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilised sources. <gallery> File:Pcb-psu-proto06.png|thumb| File:Pcb-psu-proto05.png|thumb| File:Pcb-psu-proto07.png|thumb| File:Pcb-psu-proto04.png|thumb| </gallery> Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic in: [[:File:BathazarPSU-Schematic03.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarPSU-Bill.ods|.ODS]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. Go to: [[I/O_USB|I/O hub]] or [[Keyboard|Keyboard]] 7ead1b43b4ba4ebaed61ef9f97123db8b60750c7 0 5 462 354 2020-05-20T06:14:10Z Admin 1 wikitext text/x-wiki __NOTOC__ This page documents features from more user-centric point of view. For a more engineering point of view, see [[Specifications]]. ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard:== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]], [[I/O_USB]] and [[Power Supply]]. d31006ffc87d07dbc6391bffc61c1eda76089e17 0 85 463 459 2020-05-24T10:34:09Z Admin 1 /* Balthazar I/O USB board */ wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple USB 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster USB port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. [[File:BalthazarIOusb 0.png|thumb|center]] [[File:BalthazarIOusb 2.png|thumb|center]] [[File:BalthazarIOusb 1.png|thumb|center]] PCB is ready for a prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. 6c3454bedc7014fdd7c029fc8f45ca3e90831af8 464 463 2020-05-24T10:34:43Z Admin 1 /* Balthazar I/O USB board */ wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple USB 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster USB port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. [[File:BalthazarIOusb 0.png|thumb|center]] [[File:BalthazarIOusb 2.png|thumb|center]] [[File:BalthazarIOusb 1.png|thumb|center]] PCB is ready for a prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. 2e3589fc6d776cf88f32a86cffe72a69981a1275 488 464 2020-11-11T11:56:56Z Admin 1 /* Balthazar I/O USB board */ wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple USB 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster USB port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. <gallery> File:BalthazarIOusb 0.png|thumb|top File:BalthazarIOusb 2.png|thumb|side File:BalthazarIOusb 1.png|thumb|bottom </gallery> PCB is ready for a prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. 6c890028a7c1171a3094b12438bb569963adac9c 498 488 2020-11-17T11:12:15Z Admin 1 wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple USB 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster USB port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. <gallery> File:BalthazarIOusb 0.png|thumb|top File:BalthazarIOusb 2.png|thumb|side File:BalthazarIOusb 1.png|thumb|bottom </gallery> PCB is ready for a prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. Go to: [[Keyboard|Keyboard]] or [[Power_Supply|Power Supply]] 185de9df65baaae37284aeec2c36783077078592 0 46 467 458 2020-06-17T11:57:54Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==June 2020== June is a revision month and we are applying for FSF to check on our hardware compliance, also first breadboard/prototypes will be made. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 10d2bb0e4e87caf36a7332c19df2d5b9ad8e4bcb 468 467 2020-06-17T12:01:01Z Admin 1 /* June 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. a55b825b0a143a0eccf52ecadf13183952e29083 469 468 2020-08-13T16:30:16Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==August 2020== We have been working on 3D models and overall designs for the housing. We will try to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. f76b5836697c0e65adde18d6131b7f0fffd574d3 470 469 2020-08-13T16:37:56Z Admin 1 /* July 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==August 2020== We have been working on 3D models and overall designs for the housing. We will try to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 630cebab0cfd7195d37883340efb0f1a3bb16894 471 470 2020-08-13T16:51:52Z Admin 1 /* August 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 87221717dbc145ba94f121b5a921a1e5aa24efba 472 471 2020-09-07T06:39:12Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 64ae3da8f841a4ae8aace3549a20c1c8673dc337 473 472 2020-09-22T14:29:23Z Admin 1 /* September 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. We also intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. a25cf17d93b9bea1fcf2c15988e4ea4f8d8b611d 474 473 2020-09-22T14:31:22Z Admin 1 /* September 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''HiTechnic''', '''Tipro''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 5105ab76a202f01b9736fe844e85b8092df03bb4 475 474 2020-09-22T14:32:08Z Admin 1 /* Actual news and a Balthazar development progress */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 48e7b035224116d4b10398de07bd3e8912947ff7 476 475 2020-10-06T08:18:30Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 3 PCBs and a special keyboard PCB. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during this month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. a581def7c32f04f66b768d2ccb095434927c323f 477 476 2020-11-02T17:14:42Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results will be published of our keyboard and adjoining prototype modules. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 3 PCBs and a special keyboard PCB. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during this month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. fd4a784c047c4a921c67e1ef6808a16a997cd916 478 477 2020-11-02T17:15:34Z Admin 1 /* November 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our keyboard and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 3 PCBs and a special keyboard PCB. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during this month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 44384152f8aa574bf542d5184ddb3ea5a718ddab 479 478 2020-11-02T17:16:14Z Admin 1 /* October 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our keyboard and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 3 PCBs and a special keyboard PCB. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during this or following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. b8d168f2893720b1e740d608ad3e75e5ca5e6f4e 490 479 2020-11-15T07:53:02Z Admin 1 /* November 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 3 PCBs and a special keyboard PCB. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during this or following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 5f2de14080ad4b4bf08babb4bf343222005970e0 491 490 2020-11-15T07:53:41Z Admin 1 /* October 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 3 PCBs and a special keyboard PCB. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 406d2e9a2a3077e176c79d3c56150e5451cf1ddc 507 491 2020-12-01T09:53:24Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys. Housing is getting milled and so far we are also rather happy with the preliminary results and overall dimensions. Also a rather good choice is made on speakers and camera/mic modules, so those are ordered and we await packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 3 PCBs and a special keyboard PCB. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. e6607728725562dcffcfe4a0dfe37f132d0ed4ac 508 507 2020-12-01T10:25:35Z Admin 1 /* December 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on speakers and camera/mic modules, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 3 PCBs and a special keyboard PCB. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 35cc060cad3627e3bbaa63f350d663305a525534 509 508 2020-12-01T10:27:26Z Admin 1 /* October 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on speakers and camera/mic modules, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. de27b8dd910538ad73c783957720bc6faa692e71 510 509 2020-12-02T17:12:48Z Admin 1 /* December 2020 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 2211f79f03948dd1876d30a69b5e002c0c5a161f 6 90 480 2020-11-11T10:30:48Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 91 481 2020-11-11T10:32:31Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 92 482 2020-11-11T10:33:44Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 57 500 413 2020-11-17T11:40:25Z Admin 1 wikitext text/x-wiki == Schematics == We have an early Balthazar system scheme as a block diagram upon which we develop and prototype separate boards to an interchangable compliance. [[Image:BalthazarBlockDia122.svg]] Balthazar laptop as a box consisting of: mainboard + all the perifery needed that make up a complete laptop: display, audio, keyboard, mousepad, wireless, usb, hdmi... and additionally: a buffered GPIO (general purpose in/out) connector (not that laptop usually needs it...). The technology used benefits from the current rapid mobile platform development – as do all open- source single-board computers:Banana Pi, Orange Pi 4 – and a bit more advanced Firefly- RK3399. They all use SOC (system on chip) as the miniaturized combination of CPU/GPU etc. The laptop should however be a pushed-up version of these single board computers - but still a single board computer. One format of recent computers is also the mini-pc. They are usually based on Intel or AMD laptop computer processors. LattePanda seems to be on the side of single-board-computers but uses Intel processors. Prices are also pushed up. The interchangeable module should basically be the board itself, while the stable part should be the skeleton: a specifically designed housing with display, keyboard, audio, touch-pad, power supply. To upgrade – one buys a new board and inserts it in the place of the old board. If the keyboard PCB is meant to act as the complete top cover then it's height is also defined by the LCD -> 180mm. The touch-pad module would fit above the keys (as was envisioned in the broad design considerations recently) – not as usual below the keys. The two loudspeakers go to the usual positions left and right – at the two top edges of the full-size keyboard pcb. In this way the acoustic horn effect will be at its best with LCD screen up. Ideas and some crude sketching of I/O boards and inner guts: [[File:Innerguts drawing.png|thumb|center]] The mechanical skeleton built in this manner needs additionally an USB hub board on the top right which also takes in all the necessary inner periphery (camera, keyboard). There are some of these hubs on the market, but could be made here additionally. On to four hub is prefectly ok - two externally accessed USB-connectors and two internally used for camera, keyboard. The keyboard in this rudimentary fashion acting as the top is also very thin – maybe defining the triangle-like side cross-section – since there must be enough space at the top/ back/ bottom of the lower segment. The battery pack consisting of LiIo batteries are standardized in diameter – so this defines the height. About the same size are the vertically positioned USB-A female plugs. The loudpeaker sound greatly benefits from this volume behind. Let's repeat: the interchangeable CPU/ GPU upgrade module would basically be the mini-computer mainboard itself. To upgrade – one buys a new board and inserts it in the place of the old board. If the software and file system could be kept on some SSD version of mass storage – this would be an advantage (or maybe a necessity...). Go to the: [[Power_Supply| Power Supply]], [[I/O_USB|I/O hub]] or a [[Keyboard|Keyboard]] 819749760859b7bbc4e395563f880835a13e7ba6 6 93 501 2020-11-23T17:34:18Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 95 503 2020-11-23T17:38:11Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 96 504 2020-11-23T17:39:48Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 97 505 2020-11-23T17:44:35Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 64 511 499 2020-12-22T08:41:05Z Admin 1 /* New PCB module for Balthazar has been developed. */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilised sources. <gallery> File:Pcb-psu-proto06.png|thumb| File:Pcb-psu-proto05.png|thumb| File:Pcb-psu-proto07.png|thumb| File:Pcb-psu-proto04.png|thumb| </gallery> Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic in: [[:File:BathazarPSU-Schematic03.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarPSU-Bill.ods|.ODS]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. == BalthazarPSU2 == [https://github.com/balthazar-space/balthazarPSU2 Module BalthazarPSU2] is a combined battery charger, buck-boost converter, stereo power amplifier and USB 2.0 hub. A somehow revised version of BalthazarPSU module, this one has an added USB 2.0 hub based on Microchip USB2514B which was much more readily available in Europe than GL3520 chip. Go to: [[I/O_USB|I/O hub]] or [[Keyboard|Keyboard]] 9d1130a0860f460e8147658822753ca53ae740fa 512 511 2020-12-22T08:42:30Z Admin 1 wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilised sources. <gallery> File:Pcb-psu-proto06.png|thumb| File:Pcb-psu-proto05.png|thumb| File:Pcb-psu-proto07.png|thumb| File:Pcb-psu-proto04.png|thumb| </gallery> Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic in: [[:File:BathazarPSU-Schematic03.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarPSU-Bill.ods|.ODS]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. === BalthazarPSU2 === [https://github.com/balthazar-space/balthazarPSU2 Module BalthazarPSU2] is a combined battery charger, buck-boost converter, stereo power amplifier and USB 2.0 hub. A somehow revised version of BalthazarPSU module, this one has an added USB 2.0 hub based on Microchip USB2514B which was much more readily available in Europe than GL3520 chip. Go to: [[I/O_USB|I/O hub]] or [[Keyboard|Keyboard]] e5e9aab7d6f70e696ce4002a05ae78719e68d68a 515 512 2020-12-22T08:51:40Z Admin 1 /* BalthazarPSU2 */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilised sources. <gallery> File:Pcb-psu-proto06.png|thumb| File:Pcb-psu-proto05.png|thumb| File:Pcb-psu-proto07.png|thumb| File:Pcb-psu-proto04.png|thumb| </gallery> Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic in: [[:File:BathazarPSU-Schematic03.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarPSU-Bill.ods|.ODS]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. === BalthazarPSU2 === [https://github.com/balthazar-space/balthazarPSU2 Module BalthazarPSU2] is a combined battery charger, buck-boost converter, stereo power amplifier and USB 2.0 hub. A somehow revised version of BalthazarPSU module, this one has an added USB 2.0 hub based on Microchip USB2514B which was much more readily available in Europe than GL3520 chip. <gallery> File:BalthazarPSU2-1.png|thumb| File:BalthazarPSU2-2.png|thumb| </gallery> Go to: [[I/O_USB|I/O hub]] or [[Keyboard|Keyboard]] e2e8b297372f896a06b9127752287f53470c421a 521 515 2020-12-22T17:56:26Z Admin 1 /* BalthazarPSU2 */ wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case we are trying to redesign it a bit to be more efficient and also try to add stable current "comb" that will comply to all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA max) – the most usual laptop power connector / either exterior or inserted into chasis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (Usb-A and/or Usb-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (cpu, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from adapter through the charger. When adapter is removed, the system is connected to battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack).Four external N-channel MOSFETs are used for a synchronous switching battery charger. The gate drivers are internally integrated into the IC with 6 V of gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === Input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst case RMS ripple current is half of the charging current when duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. Voltage rating of the capacitor must be higher than normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilised sources. <gallery> File:Pcb-psu-proto06.png|thumb| File:Pcb-psu-proto05.png|thumb| File:Pcb-psu-proto07.png|thumb| File:Pcb-psu-proto04.png|thumb| </gallery> Details on PSU module Features: • LiIo / LiPo battery charger 3A with wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Bathazar PSU schematic in: [[:File:BathazarPSU-Schematic03.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarPSU-Bill.ods|.ODS]] PCB ready for prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. === BalthazarPSU2 === [https://github.com/balthazar-space/balthazarPSU2 Module BalthazarPSU2] is a combined battery charger, buck-boost converter, stereo power amplifier and USB 2.0 hub. A somehow revised version of BalthazarPSU module, this one has an added USB 2.0 hub based on Microchip USB2514B which was much more readily available in Europe than GL3520 chip. <gallery> File:BalthazarPSU2-1.png|thumb| File:BalthazarPSU2-2.png|thumb| </gallery> For more on schematics, elements, bill of materials visit our [https://github.com/balthazar-space/balthazarPSU2 Github] page. Go to: [[I/O_USB|I/O hub]] or [[Keyboard|Keyboard]] 2ba64362cb381d8e6b2387300fdf738da03187c8 6 98 513 2020-12-22T08:50:02Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 99 514 2020-12-22T08:51:05Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 100 516 2020-12-22T11:29:36Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 101 517 2020-12-22T11:38:52Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 85 518 498 2020-12-22T11:40:16Z Admin 1 /* Balthazar I/O USB board */ wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple USB 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster USB port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. <gallery> File:BalthazarIOusb 0.png|thumb|top File:BalthazarIOusb 2.png|thumb|side File:BalthazarIOusb 1.png|thumb|bottom </gallery> PCB is ready for a prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. === BalthazarPSU2 + I/O unifying board === Top and bottom views of an integrated I/O hub with USB <gallery> File:BalthazarIO1PSU2.png|thumb|top File:BalthazarIO2PSU2.png|thumb|bottom </gallery> With first chip from the left is a Texas Instruments BQ24193 acts as a buck-boost converter/ battery charger another chip is a Texas Instruments TPS63020 for internal power acting as buck-boost converters (for 3.3V and 5V) Onboard is also Diodes Incorporated PAM8403 enabling 3W class-D audio amplifier while Microchip USB2514 is used as a USB 2.0 four port hub. Go to: [[Keyboard|Keyboard]] or [[Power_Supply|Power Supply]] 4662c0e02479d6ae436454324bdba0d0392a5a4b 519 518 2020-12-22T11:47:09Z Admin 1 /* BalthazarPSU2 + I/O unifying board */ wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple USB 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster USB port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. <gallery> File:BalthazarIOusb 0.png|thumb|top File:BalthazarIOusb 2.png|thumb|side File:BalthazarIOusb 1.png|thumb|bottom </gallery> PCB is ready for a prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. === BalthazarPSU2 + I/O unifying board === Top and bottom views of an integrated I/O hub with USB <gallery> File:BalthazarIO1PSU2.png|thumb|top File:BalthazarIO2PSU2.png|thumb|bottom </gallery> In a top view with first chip on the left is a Texas Instruments BQ24193 that acts as a buck-boost converter/ battery charger, another chip is a Texas Instruments TPS63020 for an internal power acting as buck-boost converters (for 3.3V and 5V) Onboard is also Diodes Incorporated PAM8403 enabling 3W class-D audio amplifier while Microchip USB2514 is used as a USB 2.0 four port hub. Go to: [[Keyboard|Keyboard]] or [[Power_Supply|Power Supply]] c53fc61e899caa8ced2fd829cba3f33d0822f920 520 519 2020-12-22T17:55:33Z Admin 1 /* BalthazarPSU2 + I/O unifying board */ wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple USB 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster USB port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. <gallery> File:BalthazarIOusb 0.png|thumb|top File:BalthazarIOusb 2.png|thumb|side File:BalthazarIOusb 1.png|thumb|bottom </gallery> PCB is ready for a prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. === BalthazarPSU2 + I/O unifying board === Top and bottom views of an integrated I/O hub with USB <gallery> File:BalthazarIO1PSU2.png|thumb|top File:BalthazarIO2PSU2.png|thumb|bottom </gallery> In a top view with first chip on the left is a Texas Instruments BQ24193 that acts as a buck-boost converter/ battery charger, another chip is a Texas Instruments TPS63020 for an internal power acting as buck-boost converters (for 3.3V and 5V) Onboard is also Diodes Incorporated PAM8403 enabling 3W class-D audio amplifier while Microchip USB2514 is used as a USB 2.0 four port hub. For more on schematics, elements, bill of materials visit our [https://github.com/balthazar-space/balthazarPSU2 Github] page. Go to: [[Keyboard|Keyboard]] or [[Power_Supply|Power Supply]] f81f8ef9b98ecb99d25bbf1aac3abe53ccbb199a 525 520 2021-02-02T18:11:32Z Admin 1 /* Balthazar I/O USB board */ wikitext text/x-wiki ==Balthazar I/O USB board== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. Here for the on-board periphery a simple USB 2.0 hub is enough. Main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point this is still mainly USB 2.0. Of course, some type of mass storage / system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster USB port – USB3.x (part of the mini-computer system-on-chip) – or PCIE bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam and optional audiocard are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched of manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better, but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is USB charging current negotiator – with no datalines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. <gallery> File:BalthazarIOusb 0.png|thumb|top File:BalthazarIOusb 2.png|thumb|side File:BalthazarIOusb 1.png|thumb|bottom File:Psiousbctop.png|thumb|top File:Psiousbcbott.png|thumb|bottom </gallery> PCB is ready for a prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimised. === BalthazarPSU2 + I/O unifying board === Top and bottom views of an integrated I/O hub with USB <gallery> File:BalthazarIO1PSU2.png|thumb|top File:BalthazarIO2PSU2.png|thumb|bottom </gallery> In a top view with first chip on the left is a Texas Instruments BQ24193 that acts as a buck-boost converter/ battery charger, another chip is a Texas Instruments TPS63020 for an internal power acting as buck-boost converters (for 3.3V and 5V) Onboard is also Diodes Incorporated PAM8403 enabling 3W class-D audio amplifier while Microchip USB2514 is used as a USB 2.0 four port hub. For more on schematics, elements, bill of materials visit our [https://github.com/balthazar-space/balthazarPSU2 Github] page. Go to: [[Keyboard|Keyboard]] or [[Power_Supply|Power Supply]] 7a962239c5b25a54cc65d6bb066fcd4edee1be15 0 46 522 510 2021-02-02T17:51:23Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 93952eadcd70bed099043fe895232eb392a982de 538 522 2021-03-10T09:59:36Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting last check up and will be soon done and uploaded on our Github, however there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 68c36887c25a5722b479e68c81a037308388d851 542 538 2021-05-14T19:44:00Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also we await for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in scarce market of RiscV SoMs. ==April 2021== The first casing were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without fan, see that cabling is neat and practical. This is a last of the pre-production design phase and we seek for quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting last check up and will be soon done and uploaded on our Github, however there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. e4de54ecf16213c9ffb49d02b9fac47951c4479c 543 542 2021-05-15T06:33:19Z Admin 1 /* April 2021 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also we await for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without fan, see that cabling is neat and practical. This is a last of the pre-production design phase and we seek for quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting last check up and will be soon done and uploaded on our Github, however there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 395c334baad6f14225871373b62b730f9fca82af 545 543 2021-06-06T18:16:11Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==June 2021== We have done CNC/3D pre-protoype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks we will look into options having those mass produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. Prospect of having a real RiscV SoM running full stack Linux are coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also we await for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without fan, see that cabling is neat and practical. This is a last of the pre-production design phase and we seek for quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting last check up and will be soon done and uploaded on our Github, however there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 4bf4eb2a4cb898919b3782e91d9b02798760a3ee 6 102 523 2021-02-02T18:08:20Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 103 524 2021-02-02T18:10:33Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 55 526 447 2021-03-09T19:42:16Z Admin 1 /* Display Controller and panel */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Display Controller and panel== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 72461f68b657a6f505704eaf060763932fadd3d0 527 526 2021-03-09T19:43:22Z Admin 1 /* Display Controller and panel */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Display Controller and panel== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 73e3ae2a47c8f7d175220be2ce0b1d941a211742 528 527 2021-03-09T19:44:33Z Admin 1 /* Display Controller and panel */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 3204129e974fd8ecd745be7b382928227617682d 544 528 2021-06-06T17:54:28Z Admin 1 /* Case */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. Chronological pictures and a phases of the development: ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 6f511548514e0b4cd0f9e18c9f4c58dc4253ba0b 559 544 2021-06-08T09:33:22Z Admin 1 /* Case */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 1934f54a2d535ed899405e0a3ceb443731c32332 560 559 2021-06-09T02:09:39Z Admin 1 /* Case */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 6cb21091bc0e76f3dd6a25d23dea46e1be8f79c9 6 104 529 2021-03-09T20:22:03Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 105 530 2021-03-09T20:23:28Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 106 531 2021-03-09T20:24:24Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 107 532 2021-03-09T20:25:21Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 108 533 2021-03-09T20:26:01Z Admin 1 Created page with "Screen panel specs and features Those are screen specifications that we took as a minimum requirements Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel..." wikitext text/x-wiki Screen panel specs and features Those are screen specifications that we took as a minimum requirements Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Here are the photos of a screen testing running in a full resolution via our power supply, keyboard controller and with the help of a clone SoM R4, running Raspbian. <gallery> File:ScreenPS1.png|thumb| File:ScreenSoM.png|thumb| File:ScreenTest1.png|thumb| File:ScreenTest2.png|thumb| </gallery> 31865c265e083f952ae043e2e7fa61d9306152e0 534 533 2021-03-09T20:26:50Z Admin 1 wikitext text/x-wiki === Screen panel specs and features === Those are screen specifications that we took as a minimum requirements Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Here are the photos of a screen testing running in a full resolution via our power supply, keyboard controller and with the help of a clone SoM R4, running Raspbian. <gallery> File:ScreenPS1.png|thumb| File:ScreenSoM.png|thumb| File:ScreenTest1.png|thumb| File:ScreenTest2.png|thumb| </gallery> ea30282e508e3375c6e9448da02dd0e68cba6e4a 535 534 2021-03-09T20:27:46Z Admin 1 wikitext text/x-wiki === Screen panel specs and features === Those are screen specifications that we took as a minimum requirements Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm === Testing and probing === Here are the photos of a screen testing running in a full resolution via our power supply, keyboard controller and with the help of a clone SoM R4, running Raspbian. <gallery> File:ScreenPS1.png|thumb| File:ScreenSoM.png|thumb| File:ScreenTest1.png|thumb| File:ScreenTest2.png|thumb| </gallery> aba2cd328501151dc271d6a26961c4a8d782dec2 0 5 536 462 2021-03-09T20:29:17Z Admin 1 wikitext text/x-wiki __NOTOC__ This page documents features from more user-centric point of view. For a more engineering point of view, see [[Specifications]]. ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard:== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]], [[I/O_USB]] and [[Power Supply]][[Screen panel]] . 1cd5478f510a287a56d654ad12a0ae6677f6039c 537 536 2021-03-09T20:30:06Z Admin 1 wikitext text/x-wiki __NOTOC__ This page documents features from more user-centric point of view. For a more engineering point of view, see [[Specifications]]. ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard:== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]], [[I/O_USB]], [[Power Supply]] and [[Screen panel]] . a7ab4f1e2e13840da161c0ef448829bdad5948c5 540 537 2021-03-10T11:38:27Z Admin 1 wikitext text/x-wiki __NOTOC__ This page documents features from more user-centric point of view. For a more engineering point of view, see [[Specifications]]. ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Current internals layouts=== Here we played with our developed boards inner layout possibilities. While designing the housing and hinging we will update those design and inner concept regularly. <gallery> File:InnerLO.png|thumb| </gallery> ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard:== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]], [[I/O_USB]], [[Power Supply]] and [[Screen panel]] . 316b2dc6233481f4e94dead00767c41ae903448a 541 540 2021-03-10T11:39:47Z Admin 1 /* Current internals layouts */ wikitext text/x-wiki __NOTOC__ This page documents features from more user-centric point of view. For a more engineering point of view, see [[Specifications]]. ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form-factor there are some improvements and novelties in approach to a physical user interface and experience. Main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned '''above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below keyboard are batteries - one small non removable and one really big that is hot-swappable - SSD bay is also below keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. Keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a totally new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Current internals layouts=== Here we played with our developed boards inner layout possibilities. While designing the housing and hinging we will update those design and the inner concept regularly. <gallery> File:InnerLO.png|thumb| </gallery> ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble.<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery's power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with general attitude towards '''FOSS''' compatibilty.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective''' - a button driven backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - colour mode with an alternance of red, green and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but remote possibility of such attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-colour polycarbonate, aluminium composite and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB on board.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone etc.<br> ==Additional adapter with an onboard:== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]], [[I/O_USB]], [[Power Supply]] and [[Screen panel]] . ee987451e8f4b7a2ad88983bc9dcc40bba0aa2bd 6 109 539 2021-03-10T11:23:41Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 110 546 2021-06-08T08:53:45Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 111 547 2021-06-08T08:54:31Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 112 548 2021-06-08T08:55:15Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 113 549 2021-06-08T08:55:57Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 114 550 2021-06-08T08:58:28Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 115 551 2021-06-08T09:27:03Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 116 552 2021-06-08T09:27:46Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 117 553 2021-06-08T09:28:57Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 118 554 2021-06-08T09:29:42Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 119 555 2021-06-08T09:30:28Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 120 556 2021-06-08T09:31:13Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 121 557 2021-06-08T09:31:56Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 122 558 2021-06-08T09:32:26Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 46 561 545 2021-07-13T09:02:56Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==July 2021== Technical drawings are done for a moulding/cutting and we will collect and choose a final candidates for speakers, mic and camera. Also a keyboard will get its final QMK file with early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile we search for other options - dreaming of an European chip supply. ==June 2021== We have done CNC/3D pre-protoype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks we will look into options having those mass produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. Prospect of having a real RiscV SoM running full stack Linux are coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also we await for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without fan, see that cabling is neat and practical. This is a last of the pre-production design phase and we seek for quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting last check up and will be soon done and uploaded on our Github, however there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 21bf5674e972abaf1cbe59f05ac183b6023537b0 564 561 2021-10-05T07:13:04Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==Ocotober 2021== We work hard on developing the proper multimodal housing choosing natural, recyclable materials. So focus this month is on a pure design, estecics, hptics, look and feel. Also a new website connected to this wiki will be done. 10, 20, 30. ==September 2021== We have commited to a cooperation with a rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is going to be added to our I/O board in form of an add on for af uther expansion. Also Radiona will help us develop "add the other keyboard" module board. ==August 2021== In August we have bundeled our modules, keyboard and screen together and got the pretty much working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for a best solution. So far we are happy how it looks (but we will need to work on a better versitile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for a moulding/cutting and we will collect and choose a final candidates for speakers, mic and camera. Also a keyboard will get its final QMK file with early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile we search for other options - dreaming of an European chip supply. ==June 2021== We have done CNC/3D pre-protoype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks we will look into options having those mass produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. Prospect of having a real RiscV SoM running full stack Linux are coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also we await for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without fan, see that cabling is neat and practical. This is a last of the pre-production design phase and we seek for quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting last check up and will be soon done and uploaded on our Github, however there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 8ef2f78ed414df4f2d2cdd9bff0b0054e1f4507a 565 564 2021-10-05T07:23:06Z Admin 1 /* Ocotober 2021 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==Ocotober 2021== We work hard on developing the proper multimodal housing choosing natural, recyclable materials. So the primary focus this month is on pure design, aesthetics, haptics, colors, look and feel. Also very soon a new website connected to this wiki will be done for better communication to a wider public and decision makers. 10, 20, 30 - no less. ==September 2021== We have commited to a cooperation with a rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is going to be added to our I/O board in form of an add on for af uther expansion. Also Radiona will help us develop "add the other keyboard" module board. ==August 2021== In August we have bundeled our modules, keyboard and screen together and got the pretty much working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for a best solution. So far we are happy how it looks (but we will need to work on a better versitile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for a moulding/cutting and we will collect and choose a final candidates for speakers, mic and camera. Also a keyboard will get its final QMK file with early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile we search for other options - dreaming of an European chip supply. ==June 2021== We have done CNC/3D pre-protoype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks we will look into options having those mass produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. Prospect of having a real RiscV SoM running full stack Linux are coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also we await for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without fan, see that cabling is neat and practical. This is a last of the pre-production design phase and we seek for quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting last check up and will be soon done and uploaded on our Github, however there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 466badf8e2b04338cb7d364be4c5c720bbe804e5 572 565 2021-10-10T19:11:03Z Admin 1 /* Ocotober 2021 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==October 2021== We work hard on developing the proper multimodal housing choosing natural, recyclable materials. So the primary focus this month is on pure design, aesthetics, haptics, colors, look and feel. Also very soon a new website connected to this wiki will be done for better communication to a wider public and decision makers. 10, 20, 30 - no less. Also we partner with [https://radiona.org/ Radiona] from Zagreb, Croatia and produce and design an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main co-processor. Exciting stuff. ==September 2021== We have commited to a cooperation with a rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is going to be added to our I/O board in form of an add on for af uther expansion. Also Radiona will help us develop "add the other keyboard" module board. ==August 2021== In August we have bundeled our modules, keyboard and screen together and got the pretty much working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for a best solution. So far we are happy how it looks (but we will need to work on a better versitile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for a moulding/cutting and we will collect and choose a final candidates for speakers, mic and camera. Also a keyboard will get its final QMK file with early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile we search for other options - dreaming of an European chip supply. ==June 2021== We have done CNC/3D pre-protoype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks we will look into options having those mass produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. Prospect of having a real RiscV SoM running full stack Linux are coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also we await for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without fan, see that cabling is neat and practical. This is a last of the pre-production design phase and we seek for quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting last check up and will be soon done and uploaded on our Github, however there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 308577a60fcd9b4af3f2c4b1030200ba662ddefe 573 572 2021-10-10T19:14:59Z Admin 1 /* October 2021 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==October 2021== We work hard on developing the proper multimodal housing choosing natural, recyclable materials. So the primary focus this month is on pure design, aesthetics, haptics, colors, look and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 - no less. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main co-processor, we will also produce all our modules with them. Exciting stuff. ==September 2021== We have commited to a cooperation with a rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is going to be added to our I/O board in form of an add on for af uther expansion. Also Radiona will help us develop "add the other keyboard" module board. ==August 2021== In August we have bundeled our modules, keyboard and screen together and got the pretty much working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for a best solution. So far we are happy how it looks (but we will need to work on a better versitile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for a moulding/cutting and we will collect and choose a final candidates for speakers, mic and camera. Also a keyboard will get its final QMK file with early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile we search for other options - dreaming of an European chip supply. ==June 2021== We have done CNC/3D pre-protoype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks we will look into options having those mass produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. Prospect of having a real RiscV SoM running full stack Linux are coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also we await for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without fan, see that cabling is neat and practical. This is a last of the pre-production design phase and we seek for quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting last check up and will be soon done and uploaded on our Github, however there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. dfd9802905d6e33a7824c715a3aba735e3af28f3 574 573 2021-10-10T19:24:37Z Admin 1 /* September 2021 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and a realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more then a few weeks of conferencing and emailing while discussing "whitepaperish" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''Tripodo''', '''SiFive''', '''Altinkaya''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in a cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> Conclusion was that Balthazar laptop has to be magical and beautiful personal computing device incorporating ethos, cooperative, inventive and innovative characteristics as a combination of those two historical characters whether they were real or a drawn. Timeline: ==October 2021== We work hard on developing the proper multimodal housing choosing natural, recyclable materials. So the primary focus this month is on pure design, aesthetics, haptics, colors, look and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 - no less. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main co-processor, we will also produce all our modules with them. Exciting stuff. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundeled our modules, keyboard and screen together and got the pretty much working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for a best solution. So far we are happy how it looks (but we will need to work on a better versitile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for a moulding/cutting and we will collect and choose a final candidates for speakers, mic and camera. Also a keyboard will get its final QMK file with early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile we search for other options - dreaming of an European chip supply. ==June 2021== We have done CNC/3D pre-protoype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks we will look into options having those mass produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. Prospect of having a real RiscV SoM running full stack Linux are coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also we await for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without fan, see that cabling is neat and practical. This is a last of the pre-production design phase and we seek for quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting last check up and will be soon done and uploaded on our Github, however there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 85adfcf63fe7bf325ab59f8463abd25355791d80 575 574 2021-10-10T19:31:21Z Admin 1 /* Actual news and a Balthazar development progress */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2021== We work hard on developing the proper multimodal housing choosing natural, recyclable materials. So the primary focus this month is on pure design, aesthetics, haptics, colors, look and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 - no less. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main co-processor, we will also produce all our modules with them. Exciting stuff. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundeled our modules, keyboard and screen together and got the pretty much working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for a best solution. So far we are happy how it looks (but we will need to work on a better versitile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for a moulding/cutting and we will collect and choose a final candidates for speakers, mic and camera. Also a keyboard will get its final QMK file with early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile we search for other options - dreaming of an European chip supply. ==June 2021== We have done CNC/3D pre-protoype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks we will look into options having those mass produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. Prospect of having a real RiscV SoM running full stack Linux are coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also we await for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without fan, see that cabling is neat and practical. This is a last of the pre-production design phase and we seek for quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting last check up and will be soon done and uploaded on our Github, however there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mock up with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screen shots of interconnected keyboard, power supply, I/O USB, screen and password input before the boot into system done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take the time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we await for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions under way. Soon we will publish photos and a first look of the casings and the other possible designs we play with and about. Also the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also we still wait for the first batch of first prototypes of 2 PCBs and a special keyboard PCB. On those we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and the types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also we will be travelling to Italy and Spain to meet with our development partners discussing some aspects of the design and some clearance in the technical solutions. After the mid September we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed description, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and some early September to CNC some of possible designs and see what would be the best fit. Also in the coming weeks we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the first prototype boards to be made and arrive apparently in late August. Also we will see into camera, speakers and other peripherals and order few samples to test and see what would be best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for I/O hub and a board that will enable a connect to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been a one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop I/O USB board and work on it to deliver files for our internal I/O USB docking board for keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So there after bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and a schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, Bill of materials and a design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also schematics and PCB for overall "modular upgrade ability and add-on" concept is in the development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also hinges are bit of an issue, but till the end of the year there will be some viable solutions. We prepare the 2 day meet-up in Weimar, somewhat later then anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attend. As it is an end to a one very exciting year, we work hard towards having everything ready before holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look really hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller '''RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. A more serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of '''EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In Weimar end of November latest mid December at the Bauhaus Uni we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few month of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got the support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation , this time at even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in a various aspects of development. Really an enthusiastic and very knowledgeable crowd. We collected ourselves old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make a use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up as for UI and UX also for proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview in expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on, until we all agreed on how, what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August in premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in a discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a totally new approach in designing the laptop investing just our own financial resources. ==June 2019== a concept for a form-factor came up and a first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water again. We won't. ==May 2019== started preliminary talks to Tripodo started on an Intellectural Propery licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending on. Domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all the sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even know how. 13065d76b896adb99621258d7ae0de6937fdf241 587 575 2021-10-10T20:30:11Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2021== We work hard on developing the proper multimodal housing choosing natural, recyclable materials. So the primary focus this month is on pure design, aesthetics, haptics, colours, look and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 - no less. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main co-processor, we will also produce all our modules with them. Exciting stuff. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 84a8f30a004f6b7071820fb6c3555ece1850a837 0 37 562 377 2021-07-29T09:38:31Z Admin 1 wikitext text/x-wiki __NOTOC__ ===Search-engine=== https://componentsearchengine.com/ ===News=== http://linuxgizmos.com/ ===Buyable Laptops=== https://www.pine64.org/pinebook-pro/ https://www.one-education.org/pages/infinity https://slimbook.es/en/ ===Designs=== https://sugarlabs.org/ https://mntmn.com/reform/ https://www.powerpc-notebook.org/en/ https://www.crowdsupply.com/sutajio-kosagi/novena ===Web Applications=== https://liveweave.com/ https://codesandbox.io/s/vanilla https://glitch.com/ ===Study and read=== http://laptopstudy.net/ 579ba6db07c7c2bca85d36d17005eedd66bbb93f 0 45 563 273 2021-07-30T05:18:28Z Admin 1 wikitext text/x-wiki A mission of '''Balthazar''' is to enable and educate end users to be private, safe and careful with their private, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy and overall security. Also additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs fully open source software stack, a derivative of '''Debian GNU/Linux''' free of a proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be not be really mandatory.<br> We are: # To design open, secure, inexpensive and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off-the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the developing process proprietary closed hardware architectures. # To support and enable low income communities and individuals all over the planet to engage in protecting their privacy, freedoms and rights on and within the internet communication. # To make computing more sustainable and reach eco-friendly footprint. # To make modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe and secure on- and off-line. 39d598a21ff22b1fddf6bcd6ad99a94c99799708 576 563 2021-10-10T19:34:21Z Admin 1 wikitext text/x-wiki The mission of '''Balthazar''' is to enable and educate end-users to be private, safe, and careful with their private, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy, and overall security. Also, additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs a fully open-source software stack, a derivative of '''Debian GNU/Linux''' free of proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be mandatory.<br> We are: # To design open, secure, inexpensive, and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the developing process proprietary closed hardware architectures. # To support and enable low-income communities and individuals all over the planet to engage in protecting their privacy, freedoms, and rights on and within internet communication. # To make computing more sustainable and reach an eco-friendly footprint. # To make a modular and granulated product that can be configured and upgraded at an affordable price. You own it - you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA-based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe, and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe, and secure on- and off-line. 684cb44a979b9f675685990590b8ca384b8c9832 0 1 566 445 2021-10-07T02:59:04Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #00ccff; margin: auto; font-size: 80%; column-count: 3;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> c78fe1d3c71e05a567b845a29ebbb2fd06d9b342 567 566 2021-10-07T03:56:03Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #85adad; margin: auto; font-size: 80%; column-count: 3;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> 97d6237b3b796b49a65d84d2afbcfbd28d234973 571 567 2021-10-09T17:19:30Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]'''. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by the default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; font-size: 80%; column-count: 3;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> d41bf358d65090d58b2f1385a3d56c01852d6fc4 577 571 2021-10-10T19:38:43Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; font-size: 80%; column-count: 3;"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> faea6c8a6bfb036eaab866b5ada149c68b9dcf9e 8 123 568 2021-10-09T17:13:24Z Admin 1 Created page with "nav.p-navbar { background: blue; }" css text/css nav.p-navbar { background: blue; } ee6d523642ff543d5f58239dbc738aadf6fdbf24 569 568 2021-10-09T17:16:38Z Admin 1 css text/css nav.p-navbar { background: #d6f6fc; } d008b52cb9158b848e1ca2a9a258a2f528ced5f5 570 569 2021-10-09T17:18:44Z Admin 1 css text/css nav.p-navbar { background: #819ba3; } 94d5867e1e2bf8fa723acc1267f18c103b72879a 0 9 578 164 2021-10-10T19:51:16Z Admin 1 wikitext text/x-wiki '''OS''' - Operating System<br> '''SW''' - Software<br> '''HW''' - Hardware<br> '''CPU''' - Central Processing Unit. A very small pile of interconnected transistors that go off or on and process the incoming instructions requests.<br> '''RAM''' - Random Access Memory. It can be written to, read from, and erased too.<br> Bigger it is, better it is for the '''CPU''' and '''OS'''. And user.<br> '''ROM''' - Read-Only Memory. It can not be written to by the user or '''OS'''. Usually contains an instruction set.<br> '''BIOS''' - Basic Input Output System. When the device is powered on it checks its physical integrity and various settings before it boots into '''OS'''.<br> It can be flushed and updated for better performance and additional '''HW''' features.<br> '''PCD''' - Personal Computing Device, a laptop, but with added extras.<br> '''FSL''' - A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software.<br> '''FOSS''' - Free and Open Source Software<br> '''GNU - GPL'''  - GNU is Not Unix, General Public Licence<br> '''FPGA''' - simply put it is a programmable [[chip or an integrated circuithttps://en.wikipedia.org/wiki/Field-programmable_gate_array|chip or an integrated circuit]] designed to be configured by a customer or a designer after manufacturing. '''RISC-V''' - '''The Free and Open RISC Instruction Set Architecture''' '''RISC-V''' is a free and open '''ISA''' enabling a new era of processor innovation through open standard collaboration.<br> '''RISC-V ISA''' delivers a new level of free, extensible software and hardware freedom on architecture, paving the way for the next 50 years of computing design and innovation. That is what '''BPCD''' is all about.<br> '''ISA''' - Instruction Set Architecture<br> '''RISC''' - Reduced Instruction Set Computer<br> '''SoC''' - System-on-Chip. One '''CPU''' to rule them all.<br> '''AMBA''' - '''Advanced Microcontroller Bus Architecture''' is a freely-available, open standard for the connection and management of functional blocks in a System-on-Chip.<br> '''SoM''' - System-on-Module. Systems on a module consist of one or more '''CPUs''' and '''GPUs''', but also have connectors for external peripherals and are to be easily exchangeable if put in a proper form-factor.<br> Think of a card that can be plugged in or taken out.<br> '''GPIO''' - General Purpose Input Output<br> '''CC''' - Creative Commons<br> '''CC-BY-SA''' - Creative Commons Attribution–Share-Alike License<br> '''ETQ''' - Excellence Through Quality<br> '''OLPC''' - One Laptop Per Child 832d424f167754cb5be3cd7378c03c29dfadb7eb 0 5 579 541 2021-10-10T20:01:46Z Admin 1 wikitext text/x-wiki __NOTOC__ This page document features from a more user-centric point of view. For a more engineering point of view, see [[Specifications]]. ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form factor, there are some improvements and novelties in approach to a physical user interface and experience. The main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones, and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned ''' above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below the keyboard are batteries - one small non-removable and one big that is hot-swappable - SSD bay is also below the keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones, and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of the I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. The keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Current internals layouts=== Here we played with our developed boards' inner layout possibilities. While designing the housing and hinging we will update those designs and the inner concept regularly. <gallery> File:InnerLO.png|thumb| </gallery> ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble. Added to it is FPGA co-processor based on a ingenious design by [https://radiona.org/ Radiona - a MakerSpace from Zagreb, Croatia] - [https://radiona.org/ulx3s/ ULX3S].<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable the Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with a general attitude towards '''FOSS''' compatibility.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective'' - a button drove backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - color mode with an alternate of red, green, and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but the remote possibility of such an attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-color polycarbonate, aluminum composite, and recyclable plastic with added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - no physical USB onboard.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone, etc.<br> ==Additional adapter with an onboard:== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]], [[I/O_USB]], [[Power Supply]] and [[Screen panel]] . 28305026a7798120f585696613e2fdc4b0c04371 0 57 580 500 2021-10-10T20:07:52Z Admin 1 wikitext text/x-wiki == Schematics == We have an early Balthazar system scheme as a block diagram upon which we develop and prototype separate boards to interchangeable compliance. [[Image:BalthazarBlockDia122.svg]] Balthazar laptop as a box consisting of mainboard + all the periphery needed that make up a complete laptop: display, audio, keyboard, mousepad, wireless, USB, HDMI... and additionally: a buffered GPIO (general purpose in/out) connector (not that laptop usually needs it...). The technology used benefits from the current rapid mobile platform development – as do all open- source single-board computers: Banana Pi, Orange Pi 4 – and a bit more advanced Firefly- RK3399. They all use SOC (system on chip) as the miniaturized combination of CPU/GPU etc. The the laptop should however be a pushed-up version of these single board computers - but still a single board computer. One format of recent computers is also the mini-pc. They are usually based on Intel or AMD laptop computer processors. LattePanda seems to be on the side of single-board computers but uses Intel processors. Prices are also pushed up. The interchangeable module should be the board itself, while the stable part should be the skeleton: a specifically designed housing with display, keyboard, audio, touch-pad, power supply. To upgrade – one buys a new board and inserts it in the place of the old board. If the keyboard PCB is meant to act as the complete top cover then its height is also defined by the LCD -> 180mm. The touch-pad module would fit above the keys (as was envisioned in the broad design considerations recently) – not as usual below the keys. The two loudspeakers go to the usual positions left and right – at the two top edges of the full-size keyboard PCB. In this way, the acoustic horn effect will be at its best with the LCD screen up. Ideas and some crude sketching of I/O boards and inner guts: [[File:Innerguts drawing.png|thumb|center]] The mechanical skeleton built in this manner needs additionally a USB hub board on the top right which also takes in all the necessary inner periphery (camera, keyboard). There are some of these hubs on the market but could be made here additionally. On to four hubs is perfectly ok - two externally accessed USB-connectors and two internally used for camera, keyboard. The keyboard in this rudimentary fashion acting as the top is also very thin – maybe defining the triangle-like side cross-section – since there must be enough space at the top/ back/ bottom of the lower segment. The battery pack is consisting of LiIo batteries standardized in diameter – so this defines the height. About the same size are the vertically positioned USB-A female plugs. The loudspeaker sound greatly benefits from this volume. Let's repeat: the interchangeable CPU/ GPU upgrade module would be the mini-computer mainboard itself. To upgrade – one buys a new board and inserts it in the place of the old board or adds something else. If the software and file system could be kept on some SSD version of mass storage – this would be an advantage (or maybe a necessity...). Go to the: [[Power_Supply| Power Supply]], [[I/O_USB|I/O hub]] or a [[Keyboard|Keyboard]] a74db299f89c86273d1feb9a7e78f982563e62ae 0 85 581 525 2021-10-10T20:09:52Z Admin 1 wikitext text/x-wiki ==Balthazar I/O USB board== IO-board means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include keyboard + trackpad, webcam, and optional audio card. USB is the usual solution for this. Here for the onboard periphery, a simple USB 2.0 hub is enough. The main mini-computer board usually provides a much better hub for 4 downstream USB devices. At this point, this is still mainly USB 2.0. Of course, some type of mass storage/system disk would be needed: microSD – and especially versions of SSD (SATA or PCIe) – directly or via USB adapter. This would benefit a faster USB port – USB3.x (part of the mini-computer system-on-chip) – or PCIe bus. '''Our solution for internal hub:''' We chose the GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, webcam, and optional audio card are USB2.0. [[File:SchemeUSB.png|thumb|center]] Internal USB devices can be switched off manually. This helps with the privacy – the microphone and webcam. For external USB devices disabling the USB power line is the same as unplugging the USB device. The "condom" approach with disabling the data lines is a bit better but solves things mostly with USB plugging into public charging stations. The TPS2540 solution is a USB charging current negotiator – with no data lines connected. A dedicated (micro-USB) charging port solves this problem. The already developed Balthazar PSU-charger has this option. <gallery> File:BalthazarIOusb 0.png|thumb|top File:BalthazarIOusb 2.png|thumb|side File:BalthazarIOusb 1.png|thumb|bottom File:Psiousbctop.png|thumb|top File:Psiousbcbott.png|thumb|bottom </gallery> PCB is ready for a prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimized. === BalthazarPSU2 + I/O unifying board === Top and bottom views of an integrated I/O hub with USB <gallery> File:BalthazarIO1PSU2.png|thumb|top File:BalthazarIO2PSU2.png|thumb|bottom </gallery> In a top view with the first chip on the left is a Texas Instruments BQ24193 that acts as a buck-boost converter/ battery charger, another chip is a Texas Instruments TPS63020 for an internal power acting as buck-boost converters (for 3.3V and 5V) Onboard is also Diodes Incorporated PAM8403 enabling 3W class-D audio amplifier while Microchip USB2514 is used as a USB 2.0 four-port hub. For more on schematics, elements, bills of materials visit our [https://github.com/balthazar-space/balthazarPSU2 Github] page. Go to: [[Keyboard|Keyboard]] or [[Power_Supply|Power Supply]] 2240803f0797d0bafdb1b1e890ed8e978d9634ef 0 58 582 506 2021-10-10T20:11:57Z Admin 1 wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our development by the Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided into left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === <gallery> File:Pcb left.png |thumb| File:Pcb right.png|thumb| File:Dm keyboard left wire diagram.png|thumb| File:Dm keyboard right wire diagram.png|thumb| </gallery> === New keyboard PCB has been developed and adopted to Balthazar dimensions === <gallery> File:Pcb-keyboard-proto05.png|thumb|top File:Pcb-keyboard-proto06.png|thumb|bottom </gallery> Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control, and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard PCB has some dimensions already defined by the LCD's dimensions of 13.3 inches in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low-cost membrane switches. A little better solution is the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics in: [[:File:BalthazarKeyboardSchematic02.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarKeyboard-Bill.ods|.ODS]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimized. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020, we have received prototypes of keyboard PCBs, ready for implementing and connecting it to the other modules and for the correct dimensioning of a case and adjoining the screen. Here are the photos of a prototype, also with a 13.3" screen. <gallery> File:Key schem.png|thumb|with the schematic File:Key scr1.png|thumb|with the screen File:Key balt2cl.png|thumb|close-up with logo </gallery> Here it is with the key modules soldered on a keyboard prototype PCB, also with the controller chip and a micro USB. <gallery> File:Key solderedon.png|thumb|with the keys soldered on File:Key back.png|thumb|back side with a controller File:Keybackclup.png|thumb|controller close-up File:Key keyonclup.png|thumb|key modules close-up </gallery> Go to: [[I/O_USB|I/O hub]] or [[Power_Supply|Power Supply]] e0a59ad00b905329d2c60fcbb3345e383598981a 0 64 583 521 2021-10-10T20:16:21Z Admin 1 wikitext text/x-wiki == Power Supply == Power Supply is an important internal part of any laptop and in our case, we are trying to redesign it a bit to be more efficient and also try to add a stable current "comb" that will comply with all ACPI requirements. === Balthazar PSU === Based on the above, these are the outlines: 1. Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton 2. Input RFI filter 3. Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) 4. LiPo battery pack single-cell charger -> from SYS voltage 5.1V 5. Large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) 6. Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger, ... 7. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) Texas Instruments BQ25713 Battery Charger -> http://www.ti.com/lit/ds/symlink/bq25713.pdf Texas Instruments BQ27Z561 Battery Fuel Gauge -> http://www.ti.com/lit/ds/symlink/bq27z561.pdf Optional: Texas Instruments BQ24210 Solar Panel Charger The valid adapter range is from 3.5 V (VVBUS_CONVEN) to 24 V (ACOV) with at least 500-mA current rating. When CHRG_OK goes HIGH, the system is powered from the adapter through the charger. When the adapter is removed, the system is connected to the battery through BATFET. Typically the battery depletion threshold should be greater than the minimum system voltage so that the battery capacity can be fully utilized for maximum battery life (meaning: rather use 2S battery pack). Four external N-channel MOSFETs are used for asynchronous switching battery chargers. The gate drivers are internally integrated into the IC with 6 V of the gate drive voltage. 30 V or higher voltage rating MOSFETs are preferred for 19 V - 20 V input voltage. === Input Capacitor === The input capacitor should have enough ripple current rating to absorb input switching ripple current. The worst-case RMS ripple current is half of the charging current when the duty cycle is 0.5 in buck mode. If the converter does not operate at 50% duty cycle, then the worst-case capacitor RMS current occurs where the duty cycle is closest to 50%. Low ESR ceramic capacitor such as X7R or X5R is preferred for input decoupling capacitor and should be placed to the drain of the high side MOSFET and source of the low side MOSFET as close as possible. The voltage rating of the capacitor must be higher than the normal input voltage level. 25 V rating or higher capacitor is preferred for 19 V - 20 V input voltage. Minimum 4 - 6 pcs of 10-μF 0805 size capacitor is suggested for 45 - 65 W adapter design. === Output Capacitor === To get good loop stability, the resonant frequency of the output inductor and output capacitor should be designed between 10 kHz and 20 kHz. The preferred ceramic capacitor is 25-V X7R or X5R for output capacitor. Minimum 6 pcs of 10-μF 0805 size capacitor is suggested to be placed by the inductor. Place the capacitors after Q4 drain. Place minimum 10 μF after the charge current sense resistor for best stability. === Schematics === [[File:Balt ps.png|thumb|center]] === Other options === BQ24171 related - 4.5V to 17V input operating voltage. Much cheaper than BQ25713 – available individually. There are several methods to damping or limiting the overvoltage spike during adapter hot plug-in. An electrolytic capacitor with high ESR as an input capacitor can damp the overvoltage spike well below the IC maximum pin voltage rating. A high current capability TVS Zener diode can also limit the overvoltage level to an IC safe level. [[File:Balt XA5018-SY8032 PSU.png|thumb|center]] VSYS Buck/ boost dc/dc converters [[File:Balt BQ24171-PSU.png|thumb|center]] === Reference to a Pinebook Pro: === Buck/ boost dc/dc converters (these are on the mainboard) This is the solution by pinebookpro v2.1 (uses RK3399 SOC – powered by 1.8V) [[File:Balt pinebookpro PSU.png|thumb|center]] === New PCB module for Balthazar has been developed. === Power supply unit based on battery charger (Texas Instruments) chip from any available source (12V / 4A mains adapter or USB power bank) and two separate buck/ boost converters for 3.3V or 5V for the necessary computer blocks (the LCD and the processor board). The board also has a stereo D-class audio power amplifier powered directly from the battery (and/or adapter) 3.6 to 4.2V - so as not to dwell on the two much more important stabilized sources. <gallery> File:Pcb-psu-proto06.png|thumb| File:Pcb-psu-proto05.png|thumb| File:Pcb-psu-proto07.png|thumb| File:Pcb-psu-proto04.png|thumb| </gallery> Details on PSU module Features: • LiIon / LiPo battery charger 3A with a wide range of input options • mains adapter 4.9-17V/3A, USB power bank 5V power sources • two independent dc-dc buck/ boost converters (each 3.3V/4A or 5V/3A) • options for USB on-the-go power supply for external devices • options for logic control of charger • manual charge enable/ disable switch • class D stereo audio power amplifier 2 x 3W • manual audio mute switch Balthazar PSU schematic in: [[:File:BathazarPSU-Schematic03.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarPSU-Bill.ods|.ODS]] PCB is ready for prototype as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimized. === BalthazarPSU2 === [https://github.com/balthazar-space/balthazarPSU2 Module BalthazarPSU2] is a combined battery charger, buck-boost converter, stereo power amplifier, and USB 2.0 hub. A somehow revised version of the BalthazarPSU module, this one has an added USB 2.0 hub based on Microchip USB2514B which was much more readily available in Europe than the GL3520 chip. <gallery> File:BalthazarPSU2-1.png|thumb| File:BalthazarPSU2-2.png|thumb| </gallery> For more on schematics, elements, Bill of Materials visit our [https://github.com/balthazar-space/balthazarPSU2 Github] page. Go to: [[I/O_USB|I/O hub]] or [[Keyboard|Keyboard]] fef3b388e0157e28f44270f33f773eec34989e9f 0 32 584 151 2021-10-10T20:17:58Z Admin 1 wikitext text/x-wiki === A concept and a guidelines for Aperture OE === This is a design proposal for a concept on the "age aperture" UI of AOE. Basic idea is that '''OS''' and its '''UI''' opens up to the child as a child's knowledge progresses using '''Balthazar''' and its security features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to exploring.<br> [[File:AOS_concept.png|center]] It is aimed to be a subtle kind of auto-parental control, but not quite so stringent, as parental control is about the permissions and control, this enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features.<br> [[File:E_box.png]] A possible example could be the "experience box" where tasks are fulfilled and a user moves on to another level with new possibilities, while also has enabled sharing within the trusted networks and with school colleagues. The complete process is encrypted and secure. 18e065db5f5d2cc6157cb800493d80a0596c3bc7 0 14 585 282 2021-10-10T20:19:56Z Admin 1 wikitext text/x-wiki === User Experience === == "Veronica" Secure Boot Environment == After the initial hardware initialization sequence and after powering on ''' Balthazar'', the first '''GUI''' that is presented is '''Secure Boot Environment''' from where the user can choose an encrypted boot device or a bootable volume. After the password is given, '''VSBE''' allows the boot sequence to be continued and the whole system is initialized. This ensures proper encryption between hardware and a currently mounted volume or a device. During the boot process, the keyboard's firmware is initialized and provides secure compression of an input stream. The usual window manager's log-in dialog is presented as one more password is required to finish the whole boot sequence into the user's GUI desktop. '''Veronica''' sits between hardware, kernel, keyboard, and a userspace and manages booting and most of the '''Balthazar''''s internal encrypted communication. == Classroom and office user-case scenarios == Different scenarios on what '''BPCD''' could do for different users are illustrated to show what is at stake, starting from the classroom to the outdoor activities out of the schools, organizations and just an average user's environments.<br> [[File:Classroom monitor security.png|center]] A teacher is monitoring students while they play with robots.<br> Each student's screen is also shown on the teacher's display.<br> It is a feature called a <big>"classroom control in a trusted networked environment".</big><br> [[File:Street security.png|center]] Young users are playing on the street in a public outdoor area in an untrusted networked environment.<br> [[File:Park security.png|center]] Afterschool activities can be performed in city parks where there is no network. The local network can be made or an access point could be set on a mobile device. f21e2f4a7a552a365ba0c41c1cd23c34f9532da5 0 28 586 283 2021-10-10T20:22:36Z Admin 1 wikitext text/x-wiki === Education in privacy, security, and general data protection in schools, high and higher educational institutions. === Here are some examples (as in pretty pictures) of why it is of utmost importance to be well educated in security, aware of what privacy is, and how to work with your data on the internet from an early age.<br> [[File:Robotic social animal.png|center|]] Humans are social animals and we like to connect to other humans, talk, and share. Same as insects, animals, and even robots are capable of doing. 2740e5773030b485855962f445940ecb7e0ce0de 0 35 588 383 2021-10-11T04:12:38Z Admin 1 wikitext text/x-wiki ===Who is this for?=== Here are some use cases and personas to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and can use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy and safety. Also, such institutions can make wide and creative use of a device’s onboard connections versatility and connectivity. Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [[Aperture Operating Environment]].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, on-line and off-line, in a [https://webkit.org/project/ '''Webkit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> incorporated <small>(a '''WARNING''' - '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is meant to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, the educational community should find the value in the overall physical sturdiness, software, and hardware sustainability of a '''BPCD'''. === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop and it comes with usually "customized" and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone - from an individual up to a big-budgeted large institution. ===But we have already had inexpensive netbooks, picturebooks, tablets, Chromebooks, and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however, they are locked in a certain software and hardware ecosystems and offer not too many security features. Also, those devices do not work without the internet, so the reputation of such devices is often seen as "personal data collecting devices", so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on a mere profit, but on protecting and also educating users of all ages on how '''not''' to engage in voluntary dissemination of their private data all over the internet, often being used as bait for large companies that take advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behavior. '''BPCD''' is aimed to inexpensively enable end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have the system invaded or spied on by any 3<small>rd</small> party. === What do you want? === We want to enable and support low-income individuals and communities all over the planet with a powerful, open, and secure computing experience, while carefully partnering with “humane” and ethical corporations along the way. Those will participate as co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Alternatively, they can build their curriculum around the '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education'', educational institutions, various charities, foundations, and '''EU''' initiatives, so we can only hope they can deliver expected behavior and practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some of the '''OLPC''' product design innovations and features, that are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety, and personal data protection and encrypted shared data or a retention of the same in its own “cloud”. === But... A ''"Cloud"'' is free, cool, useful and hype. === Remember - a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''"share"''' your data with them.<br> === So, why should me or my children want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could make an impact.  New generations need to learn and understand the importance of being secure and how to care about their data.<br> It is also aimed at "the makers of the things" with 19 GPIO connectors on-board enabling users of all ages in control, testing, and programming sensors, actuators, and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. 47750937b516191011986787237064a19934bbfe 589 588 2021-10-11T04:28:11Z Admin 1 wikitext text/x-wiki ===Who is this for?=== Here are some use cases and personas to which '''Balthasar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and can use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy, and safety. Also, such institutions can make wide and creative use of a device’s onboard connections versatility and connectivity. Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [[Aperture Operating Environment]].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, online and off-line, in a [https://webkit.org/project/ '''WebKit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> Incorporated <small>(a '''WARNING''' — '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, the educational community should find the value in the overall physical sturdiness, software, and hardware sustainability of a '''BPCD'''. === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop, and it comes with usually “customized” and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone — from an individual up to a big-budgeted large institution. ===But we have already had inexpensive netbooks, picturebooks, tablets, Chromebooks, and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however, they are locked in a certain software and hardware ecosystems and offer not too many security features. Also, those devices do not work without the internet, so the reputation of such devices is often seen as “personal data collecting devices”, so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on profit. Imperative here is protecting and educating users of all ages on how '''not''' to engage in voluntary dissemination of their private data all over the internet, that often being used as bait by large companies. Those do take advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable the end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have the system invaded or spied on by any 3<small>rd</small> party. === What do you want? === We want to enable and support low-income individuals and communities all over the planet with a powerful, open, and secure computing experience, while carefully partnering with “humane” and ethical corporations along the way. Those will participate as co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Alternatively, they can build their curriculum around the '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education'', educational institutions, various charities, foundations, and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some '''OLPC''' product design innovations and features. Those are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety, and personal data protection and encrypted shared data or a retention of the same in its own so-called “cloud”. === But… A ''” Cloud”'' is free, cool, useful and hype. === Remember — a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''” share”''' your data with them.<br> === So, why should me or my children want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could and should make an impact.  New generations need to learn and understand the importance of being secure and how to care about their data.<br> It is also aimed at “the makers of the things” with 36 GPIO connectors on-board enabling students and users of all ages to control, test, and program sensors, actuators, and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. 70cea9b3312481f26ec7a4721431625b1e5b1082 590 589 2021-10-11T04:28:37Z Admin 1 wikitext text/x-wiki ===Who is this for?=== Here are some use cases and personae to which '''Balthasar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and can use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy, and safety. Also, such institutions can make wide and creative use of a device’s onboard connections versatility and connectivity. Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [[Aperture Operating Environment]].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, online and off-line, in a [https://webkit.org/project/ '''WebKit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> Incorporated <small>(a '''WARNING''' — '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, the educational community should find the value in the overall physical sturdiness, software, and hardware sustainability of a '''BPCD'''. === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop, and it comes with usually “customized” and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone — from an individual up to a big-budgeted large institution. ===But we have already had inexpensive netbooks, picturebooks, tablets, Chromebooks, and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however, they are locked in a certain software and hardware ecosystems and offer not too many security features. Also, those devices do not work without the internet, so the reputation of such devices is often seen as “personal data collecting devices”, so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on profit. Imperative here is protecting and educating users of all ages on how '''not''' to engage in voluntary dissemination of their private data all over the internet, that often being used as bait by large companies. Those do take advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable the end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have the system invaded or spied on by any 3<small>rd</small> party. === What do you want? === We want to enable and support low-income individuals and communities all over the planet with a powerful, open, and secure computing experience, while carefully partnering with “humane” and ethical corporations along the way. Those will participate as co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Alternatively, they can build their curriculum around the '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education'', educational institutions, various charities, foundations, and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some '''OLPC''' product design innovations and features. Those are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety, and personal data protection and encrypted shared data or a retention of the same in its own so-called “cloud”. === But… A ''” Cloud”'' is free, cool, useful and hype. === Remember — a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''” share”''' your data with them.<br> === So, why should me or my children want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could and should make an impact.  New generations need to learn and understand the importance of being secure and how to care about their data.<br> It is also aimed at “the makers of the things” with 36 GPIO connectors on-board enabling students and users of all ages to control, test, and program sensors, actuators, and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. b8fb42063788460a6b3e450015be33ee5448795a 591 590 2021-10-11T04:29:53Z Admin 1 wikitext text/x-wiki ===Who is this for?=== Here are some use cases and personae to which '''Balthasar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are expected to be skilled and aware enough, so they can quickly understand UI, UX and can use additional AES encryption for the prevention of official and personal data protection through secure productivity apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy, and safety. Also, such institutions can make wide and creative use of a device’s onboard connections versatility and connectivity. Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [[Aperture Operating Environment]].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, online and off-line, in a [https://webkit.org/project/ '''WebKit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> Incorporated <small>(a '''WARNING''' — '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, the educational community should find the value in the overall physical sturdiness, software, and hardware sustainability of a '''BPCD'''. === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop, and it comes with usually “customized” and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone — from an individual up to a big-budgeted large institution. ===But we have already had inexpensive netbooks, picturebooks, tablets, Chromebooks, and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however, they are locked in a certain software and hardware ecosystems and offer not too many security features. Also, those devices do not work without the internet, so the reputation of such devices is often understood as “personal data collecting devices”, so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is not based on profit. Imperative here is protecting and educating users of all ages on how '''not''' to engage in voluntary dissemination of their private data all over the internet, that often being used as bait by large companies. Those do take advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable the end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have the system invaded or spied on by any 3<small>rd</small> party. === What do you want? === We want to enable and support low-income individuals and communities all over the planet with a powerful, open, and secure computing experience, while carefully partnering with “humane” and ethical corporations along the way. Those will participate as co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Alternatively, they can build their curriculum around the '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education'', educational institutions, various charities, foundations, and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some '''OLPC''' product design innovations and features. Those are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety, and personal data protection and encrypted shared data or a retention of the same in its own so-called “cloud”. === But… A ''” Cloud”'' is free, cool, useful and hype. === Remember — a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''” share”''' your data with them.<br> === So, why should me or my children want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could and should make an impact.  New generations need to learn and understand the importance of being secure and how to care about their data.<br> It is also aimed at “the makers of the things” with 36 GPIO connectors on-board enabling students and users of all ages to control, test, and program sensors, actuators, and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. 21df8c8badc711b9007769754eef299790c54842 592 591 2021-10-11T04:59:50Z Admin 1 wikitext text/x-wiki ===Who is this for?=== We are not personal computers' manufacturer, and we do not sell, produce or manufacture anything, except concepts and designs. Here are some use cases and personae to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are skilled and aware enough, so they can quickly understand UI, UX, hardware features and will use additional AES encryption for the prevention of official and personal data protection through secure productivity suite of apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy, and safety. Also, such institutions can make wide and creative use of a device’s software, onboard connections, versatility, and connectivity. Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [[Aperture Operating Environment]].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, online and off-line, in a [https://webkit.org/project/ '''WebKit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> Incorporated <small>(a '''WARNING''' — '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, the educational community should find the value in the overall physical sturdiness, software, and hardware sustainability of a '''BPCD'''. === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop, and it comes with usually “customized” and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone — from an individual up to a big-budgeted large institution. ===But we have already had inexpensive netbooks, picturebooks, tablets, Chromebooks, and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however, they are locked in a certain software and hardware ecosystems and offer not too many security features. Also, those devices do not work without the internet, so the reputation of such devices is often understood as “personal data collecting devices”, so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is altruistic and non-profit. Imperative here is protecting and educating users of all ages on how '''not''' to engage in voluntary dissemination of their private data all over the internet, that often being used as bait by large companies. Those do take advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable the end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have the system invaded or spied on by any 3<small>rd</small> party. === What do you want? === We want to enable and support low-income individuals and communities all over the planet with a powerful, open, and secure computing experience, while carefully partnering with “humane” and ethical corporations along the way. Those will participate as co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Alternatively, they can build their curriculum around the '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education'', educational institutions, various charities, foundations, and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some '''OLPC''' product design innovations and features. Those are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety, and personal data protection and encrypted shared data or a retention of the same in its own so-called “cloud”. === But… A ''” Cloud”'' is free, cool, useful and hype. === Remember — a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''” share”''' your data with them.<br> === So, why should me or my children want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could and should make an impact.  New generations need to learn and understand the importance of being secure and how to care about their data.<br> It is also aimed at “the makers of the things” with 36 GPIO connectors on-board enabling students and users of all ages to control, test, and program sensors, actuators, and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. 29cabddd1762f687b67cce9d19009dd1694105a3 593 592 2021-10-11T05:02:22Z Admin 1 wikitext text/x-wiki ===Who is this for?=== We are not personal computers' manufacturer. We do not sell, mass-produce or manufacture anything, except concepts, Open Source designs and fully functional prototypes for demonstration purposes and presentations. Here are some use cases and personae to which '''Balthazar''' just might appeal: '''1.''' '''An average basic internet user''' that requires some default security and develops a certain awareness on its data privacy and is friendly-forced upon using the security and encryption through the default usage of the device. '''2.''' '''Advanced computer users, journalists, governmental and public institution's workers''' that need secure hardware and software features to prevent an intrusion and the theft of sensitive data.<br> They are skilled and aware enough, so they can quickly understand UI, UX, hardware features and will use additional AES encryption for the prevention of official and personal data protection through secure productivity suite of apps and tools. '''3.''' '''Educational institutions''' that will teach online security, privacy, and safety. Also, such institutions can make wide and creative use of a device’s software, onboard connections, versatility, and connectivity. Proposed '''[[Aperture Operating Environment|AOE]]''' for children and schools mode windowing environment and its [[User Interface]] and [[User Experience]] is utilising age-adoptive [[Aperture Operating Environment]].<br> For more advanced use, now just as an example, it will feature a fully functional, secure, online and off-line, in a [https://webkit.org/project/ '''WebKit'''] or a [https://www.chromium.org/blink '''Blink'''] browser<br> Incorporated <small>(a '''WARNING''' — '''not''' a '''secure''' page)</small> '''[http://desktop.ljudmila.net/ Workbench]''' that will have a range of fully customizable productivity apps, such as Text, WebDev, Paint and SVG editors amongst the other examples shown there.<br> This Workbench is to be based on a new [https://wiki.ljudmila.org/WebShell WebShell] environment still under the development. Added to it all, the educational community should find the value in the overall physical sturdiness, software, and hardware sustainability of a '''BPCD'''. === Why yet another laptop? === It is very expensive to buy an “advanced” or a secure laptop, and it comes with usually “customized” and mostly proprietary software that bounds a user to a manufacturer. This is where '''BPCD''' comes in at the most possible lowest retail price that should be affordable to everyone — from an individual up to a big-budgeted large institution. ===But we have already had inexpensive netbooks, picturebooks, tablets, Chromebooks, and alike.=== '''Google''', '''Samsung''', '''Acer''', '''Asus''', '''Dell''' and the other respective manufacturers already make inexpensive and lightweight laptops, however, they are locked in a certain software and hardware ecosystems and offer not too many security features. Also, those devices do not work without the internet, so the reputation of such devices is often understood as “personal data collecting devices”, so that doesn't help to create a positive image towards such products. It is the fact that such devices also appear less flexible towards full '''FOSS''', '''GNU-GPL''' and '''EOMA''' guidelines that we want to use and set up as another standard for the new internet age. Such ethical standard is altruistic and non-profit. Imperative here is protecting and educating users of all ages on how '''not''' to engage in voluntary dissemination of their private data all over the internet, that often being used as bait by large companies. Those do take advantage and make amazing profits because of such illiterate, involuntary, unconsciousness and irresponsible behaviour. '''BPCD''' is aimed to inexpensively enable the end-user to control all the inputs via physical hardware switches and security dongles, preventing even a remote possibility to have the system invaded or spied on by any 3<small>rd</small> party. === What do you want? === We want to enable and support low-income individuals and communities all over the planet with a powerful, open, and secure computing experience, while carefully partnering with “humane” and ethical corporations along the way. Those will participate as co-creators and will get '''Balthazars''' to give away, rent or borrow '''BPCD''' to those who are unable to afford it. Alternatively, they can build their curriculum around the '''Balthazar''' ecosystem. We loosely partner with '''LEGO® Education, Google Education'', educational institutions, various charities, foundations, and '''EU''' initiatives, so we can only hope they can deliver expected behaviour and practice. So, '''Balthazar''' is <strong>NOT</strong> '''OLPC'''-alike, but it does follow some '''OLPC''' product design innovations and features. Those are adopted and improved for today’s performance requirements, strictly focusing on privacy, safety, and personal data protection and encrypted shared data or a retention of the same in its own so-called “cloud”. === But… A ''” Cloud”'' is free, cool, useful and hype. === Remember — a ''“Cloud”'' is just other people’s or corporations’ computers that store your data when you do '''” share”''' your data with them.<br> === So, why should me or my children want one? === [[Education]] being a very important issue today all over the planet is yet another field where affordable '''BPCD''' could and should make an impact.  New generations need to learn and understand the importance of being secure and how to care about their data.<br> It is also aimed at “the makers of the things” with 36 GPIO connectors on-board enabling students and users of all ages to control, test, and program sensors, actuators, and other electronic devices and gadgets from literally every manufacturer. Added to it, its value is increased with an optional add-on module with '''LEGO®'''-specific RJ-12 and '''Power Functions''' connectors. 78813e8e827a987e1c73370c09b442e5de4a0399 4 3 594 429 2021-10-11T18:47:19Z Admin 1 wikitext text/x-wiki Balthazar is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is part of an effort to revive and accelerate EU integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. eb9544abfc9db4038673dee0782acc5531851326 596 594 2021-10-18T12:56:33Z Admin 1 wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2020 and 2021 (ending June) can be found [[Balthazar_Costs_20-21.pdf|here]]. 4ee055cb439781a56e260e28f8c21a16e9b5f1f7 597 596 2021-10-18T12:58:14Z Admin 1 wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2020 and 2021 (ending June) can be found ⇾ [[File:Balthazar Costs 20-21.pdf|thumb|here]] . 56c2f2b820111eee160ad35d58e312a05dbceb08 598 597 2021-10-18T13:05:46Z Admin 1 wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2020 and 2021 (ending June) ⇾ [[File:Balthazar Costs 20-21.pdf|left|thumb|costs of materials for the development]] f9b944c2893145bdc76909a0c75bafd3a864605c 599 598 2021-10-18T13:08:33Z Admin 1 wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2020 and 2021 (ending June) ⇾ c9e28713dd68badca18e379e66b093dbbcc85a35 601 599 2021-10-18T13:20:39Z Admin 1 wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2020 and 2021 (ending June) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021]] cba31f8dd2b3af5088db6b3976315e2a9b6fb77b 604 601 2021-10-21T10:49:03Z Admin 1 wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2020 and 2021 (ending June) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 — electronic parts]] ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board. — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ — ODroid XU4 — 85 Euro Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona — as a gift (thanx a lot!) 7fba5f1b915b9cb66d41d3891bd9d792742cd8b9 605 604 2021-10-21T10:51:33Z Admin 1 /* Transparency and the ethics */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2020 and 2021 (ending June) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 — electronic parts]] ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board. — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ — ODroid XU4 — 85 Euro Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro 2e76f7543e2b4a9dc977df02f4e26842d6386071 606 605 2021-10-21T10:53:09Z Admin 1 /* Transparency and the ethics */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2020 and 2021 (ending June) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 — electronic parts list]]<br> ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board. — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ — ODroid XU4 — 85 Euro Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro 5759b2b141c0a600fcd3b98d484de99e9916e1f1 607 606 2021-10-21T10:55:10Z Admin 1 /* Development boards bought or used for the development in 2019–2021: */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2020 and 2021 (ending June) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 — electronic parts list]]<br> ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board. — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ used — ODroid XU4 — 185 Euro including: Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro 3aa0dcde4225a0cb1d5fa65324eaaca9af2d2111 608 607 2021-10-21T10:55:35Z Admin 1 /* Development boards bought or used for the development in 2019–2021: */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2020 and 2021 (ending June) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 — electronic parts list]]<br> ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board. — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ used — ODroid XU4 — 185 Euro including: Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro fc09d327204d3ce322295a62d328a6744ad4121d 609 608 2021-10-21T11:01:06Z Admin 1 /* Transparency and the ethics */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2019 and 2021 (ending June) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 — electronic parts list]]<br> ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board — used — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ — used — ODroid XU4 — 185 Euro including: Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro 7570dd79cab95a24cdf837cf48d26675a4d1dfc4 610 609 2021-10-21T11:01:43Z Admin 1 /* Transparency and the ethics */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2019 and 2021 (ending June 2021) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 — electronic parts list]]<br> ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board — used — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ — used — ODroid XU4 — 185 Euro including: Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro 7a8170086055fcb37fafe6049fff3e49e052d4d0 6 124 595 2021-10-18T12:48:29Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 125 600 2021-10-18T13:09:05Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 4 4 602 25 2021-10-18T16:19:47Z Admin 1 wikitext text/x-wiki Everything Balthazar does is FOSS and GPL v2, GPL v3 and copy-left with a CC-by-SA 4.0, CERN OSHW, where licenses apply, except partners’ respective copyrights and trademarks. Otherwise, you are on your own around here. 3bc22ca755ff4767e868ee6d22c060c24e821ea6 4 7 603 17 2021-10-18T16:20:47Z Admin 1 wikitext text/x-wiki '''We guarantee safe, secure and private browsing of our pages.'''<br> We will not use '''IN ANY CASE, ANY OF YOUR DATA''' even if you submit some.<br> 3fcc70e9ee7da5e0229938717c868fdec8488e7f 4 3 611 610 2021-10-21T11:20:40Z Admin 1 /* Development boards bought or used for the development in 2019–2021: */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2019 and 2021 (ending June 2021) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 — electronic parts list]]<br> ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board — used — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ — used — ODroid XU4 — 185 Euro including: Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro cd5edf93c978fa96826fb29f55ffc7386ca9b585 612 611 2021-10-21T11:23:16Z Admin 1 /* Development boards bought or used for the development in 2019–2021: */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2019 and 2021 (ending June 2021) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 — electronic parts list]]<br> ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board — used — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ — used — ODroid XU4 — 185 Euro including: Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona, Zagreb — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro total spent (June 2021) — '''1215 Euro''' 65b14f9ab4a913fa065f5bdc2bebd03d247f7cf0 613 612 2021-10-21T11:27:05Z Admin 1 /* Development boards bought or used for the development in 2019–2021: */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2019 and 2021 (ending June 2021) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 — electronic parts list]]<br> ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board — used — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ — used — ODroid XU4 — 185 Euro including: Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona, Zagreb — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro — Total expenses (June 2021) — '''1215 Euro'''— e0f631ceb01146a9a9cf72b693f5ac888a896a29 614 613 2021-10-21T11:27:54Z Admin 1 /* Development boards bought or used for the development in 2019–2021: */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2019 and 2021 (ending June 2021) ⇾ [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 — electronic parts list]]<br> ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board — used — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ — used — ODroid XU4 — 185 Euro including: Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona, Zagreb — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro ------------------------------------------ Total expenses (June 2021) — '''1215 Euro''' 7da7c2aaf7aa99314abd70c00b408a079f10229f 615 614 2021-10-21T11:30:01Z Admin 1 /* Transparency and the ethics */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2019 and 2021 (ending June 2021) ⇾ QR [[File:Qrcode_balthazar.space.png|thumb|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 (June) — electronic parts list]]<br> ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board — used — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ — used — ODroid XU4 — 185 Euro including: Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona, Zagreb — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro ------------------------------------------ Total expenses (June 2021) — '''1215 Euro''' 6f817f8a1403fbf39cb5eea3dd1983f4c032d1e3 616 615 2021-10-21T11:52:17Z Admin 1 /* Transparency and the ethics */ wikitext text/x-wiki '''Balthazar''' is an international consortium that sets in motion and leads a new approach in the design and the construction of a full CERN Open Hardware Licence and GNU-GPL compliant FOSS laptop as a personal computing device. It is a minor part of an effort to revive and accelerate '''EU''' integrated circuits and electronics industry. Personal Computing Device will contain all the hardware and innovative software features and new set of precautions to prevent any 3rd party intrusion into the system. The consortium consists of an industry and academia personae, and it is applied for a Common Conservancy status for the further preservation of the project. We keep our designs open and encourage makers, enthusiasts, and FOSS software developers to create a secure, easy to use and intuitive user-friendly hardware and software for the Balthazar Personal Computing Device or following our designs create something entirely new. == '''Transparency and the ethics''' == Costs of the development for the years 2019 and 2021 (ending June 2021) ⇾ [[File:Qrcode_balthazar.space.png|thumb|center|100px|link=https://balthazar.space/w/images/b/bd/Balthazar_Costs_20-21.pdf|Balthazar developing costs 2020-2021 (June) — electronic parts list]] ==== Development boards bought or used for the development in 2019–2021: ==== — [https://www.kickstarter.com/projects/udoo/udoo-android-linux-arduino-in-a-tiny-single-board/description UDOO Quad/Dual] board — used — Nano Pi from Friendly Arm — 10 EURO + tax — ODroid U3+ — used — ODroid XU4 — 185 Euro including: Cloud Shell case — 30 Euro Hard Disk — 60 Euro Display 2.5 inch — 10 Euro — HiFIve1 Rev B Development Board — 100 Euro — SiFive HiFive Unmatched Linux Development Board — still waiting for it — 730 Euro including tax and shipping — ULX3S FPGA board from Radiona, Zagreb — as a gift (thanx a lot!) — Rii Wireless keyboard — 40 Euro — SD cards, various expenses — 50 Euro ------------------------------------------ Total expenses (June 2021) — '''1215 Euro''' a53584185b2f32bb684b032b2ba95648e950c13e 0 46 617 587 2021-10-21T12:06:52Z Admin 1 /* October 2021 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 9f332ffc3ddbf1c197e34b2897cdcb1849718241 627 617 2021-12-07T19:26:49Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a working version. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 37e754f3992677b080c7f44b32d7c742deca884b 628 627 2021-12-07T19:27:44Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 742db5ea36c9af8830166e6c0885ed4f25eaa44a 629 628 2022-01-03T18:39:25Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==January 2022== Starting the third year of Balthazar's development and getting preliminary case designs soon to get published on line and on our Github page. Also we are sorting out and updating the all the documentation on a Github. We are also readying the third iteration of a keyboard with standard slim Cherry style click-switches. Ports and I/O HAT module is still being deep in the design process, also a bit lacking options there and slightly changing designs due to the continuus shortage and a choice of chips. But we will get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. b6b5430398683a958c26b987c335100284590665 630 629 2022-01-03T18:41:36Z Admin 1 /* January 2022 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==January 2022== Starting the third year of Balthazar's development and getting preliminary case designs soon to get published online and on our GitHub page. Also, we are sorting out and updating the all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click-switches. Ports and I/O HAT module is still being deep in the design process, also a bit lacking options there and slightly changing designs due to the continuous shortage and a choice of chips. But we will get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 07eee8dba81e33d4dfcf5b72a44192951a9680d8 631 630 2022-01-03T18:47:13Z Admin 1 /* January 2022 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''EOMA68''', '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. a1314f51c148dbfe71185044acb93fd6b795fa93 633 631 2022-01-07T13:20:08Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 3dc99db6bcfca23156b071f82722b1276501d64f 634 633 2022-02-01T10:48:08Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preleiminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. aeed9022d7a98ee2e5c32f6f02e512398a0291ef 642 634 2022-02-11T10:36:14Z Admin 1 /* February 2022 */ wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 87f96acd620b4701e1142bee81369f6e56bff281 651 642 2022-05-09T06:47:55Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 00392629ddaa9115d9790fc6f4dea782d4bfe1cc 0 37 618 562 2021-10-21T19:04:57Z Admin 1 /* Web Applications */ wikitext text/x-wiki __NOTOC__ ===Search-engine=== https://componentsearchengine.com/ ===News=== http://linuxgizmos.com/ ===Buyable Laptops=== https://www.pine64.org/pinebook-pro/ https://www.one-education.org/pages/infinity https://slimbook.es/en/ ===Designs=== https://sugarlabs.org/ https://mntmn.com/reform/ https://www.powerpc-notebook.org/en/ https://www.crowdsupply.com/sutajio-kosagi/novena ===Web Applications=== https://liveweave.com/ https://codesandbox.io/s/vanilla https://glitch.com/ http://websh.org/ ===Study and read=== http://laptopstudy.net/ 8cc4237ec1bcfd616591ac1da0cb0680d728a46e 0 1 619 577 2021-11-23T16:58:17Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; font-size: 80%; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> b2ef4758c36050d26002349690fededf13c7c36d 625 619 2021-11-23T17:12:31Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''EOMA''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> 1530c9ebc86254804a600879c7de39d3ed8adc60 632 625 2022-01-07T13:14:32Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS..?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> d7ab48de4438684ab723b20240009b25aa54f534 641 632 2022-02-11T10:34:38Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> 7c73be9a6864fa70667c13494b5e8b66ef24be30 652 641 2022-05-16T10:49:13Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Links]] and [[Documentation]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> e0ebe2d075a7457fb94441a91a2b0f27c275ae31 653 652 2022-05-16T10:49:47Z Admin 1 wikitext text/x-wiki __NOTOC__ == <strong>a Personal Computing Device</strong> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Documentation]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> ea61a51f10076a4e34734b4b26c1e56b3a20b657 656 653 2022-05-16T11:26:59Z Admin 1 wikitext text/x-wiki __NOTOC__ == <center><strong>a Personal Computing Device</strong></center> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Bpcd1 sketch.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Documentation]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> 51339d3fa40a4dee9316f0535eb4424c18474df2 8 123 620 570 2021-11-23T16:58:44Z Admin 1 css text/css nav.p-navbar { background: #819ba3; } .menue a { color: white; } 13172f6f2884ef626fadbd477f3f89ad7c55f968 621 620 2021-11-23T16:59:55Z Admin 1 css text/css nav.p-navbar { background: #819ba3; } a { color: #819ba3; } .menue a { color: white; } .menue a:visited { color: white; } 1aa0b0218f6eb0f672c5c909c2fde278e68c9454 622 621 2021-11-23T17:01:18Z Admin 1 css text/css nav.p-navbar { background: #819ba3; } a[href].external { color: #819ba3; } a { color: #819ba3; } .menue a { color: white; } .menue a:visited { color: white; } 9f43a9f4d245d7e12aba69f6bb7f1cbc2861b6f7 623 622 2021-11-23T17:01:46Z Admin 1 css text/css nav.p-navbar { background: #819ba3; } a[href].external { color: #819ba3; } a { color: #819ba3; } .menue a { color: white; } .menue a[href].external { color: white; } ccf2ab48a567dd54c082c28bde8a80d980307f5b 624 623 2021-11-23T17:11:08Z Admin 1 css text/css nav.p-navbar { background: #819ba3; } a[href].external { color: #819ba3; } a { color: #819ba3; } .menue a { color: white; } .menue a[href].external { color: white; } .menue { font-size: larger; } fd57dacd18830f369ac5bc0f82c8fa05e7d4d726 626 624 2021-11-23T17:13:55Z Admin 1 css text/css nav.p-navbar { background: #819ba3; } a[href].external { color: #819ba3; } a { color: #819ba3; } .menue a { color: white; } .menue a[href].external { color: white; } .menue { font-size: larger; padding: 1rem 0.5rem; } 4179a3aef3963ae62734add9620c7dff4529624b 0 14 635 585 2022-02-11T08:11:02Z Admin 1 wikitext text/x-wiki === User Experience === == "Veronica" Secure Boot Environment == After the initial hardware initialization sequence and after powering on ''' Balthazar'', the first '''GUI''' that is presented is '''Secure Boot Environment''' from where the user can choose an encrypted boot device or a bootable volume. After the password is given, '''VSBE''' allows the boot sequence to be continued and the whole system is initialized. This ensures proper encryption between hardware and a currently mounted volume or a device. During the boot process, the keyboard's firmware is initialized and provides secure compression of an input stream. The usual window manager's log-in dialog is presented as one more password is required to finish the whole boot sequence into the user's GUI desktop. '''Veronica''' sits between hardware, kernel, keyboard, and a user space and manages booting and most of the '''Balthazar''''s internal encrypted communication. == Classroom and office user-case scenarios == Different scenarios on what '''BPCD''' could do for different users are illustrated to show what is at stake, starting from the classroom to the outdoor activities out of the schools, organizations and just an average user's environments.<br> [[File:Classroom monitor security.png|center]] A teacher is monitoring students while they play with robots.<br> Each student's screen is also shown on the teacher's display.<br> It is a feature called a <big>"classroom control in a trusted networked environment".</big><br> [[File:Street security.png|center]] Young users are playing on the street in a public outdoor area in an untrusted networked environment.<br> [[File:Park security.png|center]] After school activities can be performed in city parks where there is no network. The local network can be made or an access point could be set on a mobile device. a2a214a671f4633c6a7a7478256ae2a9c68bb6e1 0 32 636 584 2022-02-11T08:12:42Z Admin 1 wikitext text/x-wiki === A concept and a guidelines for Aperture OE === This is an additional design proposal for a concept on the “age aperture” UI of AOE. Basic idea is that '''OS''' and its '''UI''' opens up to the child as a child's knowledge progresses using '''Balthazar''' and its security features. When tasks needed to jump to another level are completed, a new level of learning and possibilities is open to exploring.<br> [[File:AOS_concept.png|center]] It is aimed to be a subtle kind of auto-parental control, but not quite so stringent, as parental control is about the permissions and control. This enables the younger user to control entirely own freedom level by being engaged with the Balthazar and its features.<br> [[File:E_box.png]] A possible example could be the "experience box" where tasks are fulfilled and a user moves on to another level with new possibilities, while also has enabled sharing within the trusted networks and with school colleagues. The complete process is encrypted and secure. 94490b11f4607df2afae72c360847ffeb1232fe6 0 5 637 579 2022-02-11T08:15:14Z Admin 1 wikitext text/x-wiki __NOTOC__ This page document features from a more user-centric point of view. For a more engineering point of view, see [[Specifications]]. ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form factor, there are some improvements and novelties in approach to a physical user interface and experience. The main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones, and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned ''' above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below the keyboard are batteries - one small non-removable and one big that is hot-swappable - SSD bay is also below the keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones, and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of the I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. The keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Current internals layouts=== Here we played with our developed boards' inner layout possibilities. While designing the housing and hinging we will update those designs and the inner concept regularly. <gallery> File:InnerLO.png|thumb| </gallery> ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble. Added to it is FPGA co-processor based on a ingenious design by [https://radiona.org/ Radiona - a MakerSpace from Zagreb, Croatia] - [https://radiona.org/ulx3s/ ULX3S].<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable the Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with a general attitude towards '''FOSS''' compatibility.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective'' - a button drove backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - color mode with an alternate of red, green, and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but the remote possibility of such an attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-color polycarbonate, or aluminum composite, and recyclable plastic with maybe added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - a bit secured USB onboard.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone, etc.<br> ==Additional adapter with an onboard:== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]], [[I/O_USB]], [[Power Supply]] and [[Screen panel]] . 6cceb9858103a053cc724219f9734dacba7c56ee 0 55 638 560 2022-02-11T09:29:56Z Admin 1 wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 9245dacc65eb85ee18966ed8b4b5cc8e7031e100 644 638 2022-04-12T09:54:06Z Admin 1 wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 6cedd6f80a061ecc31bc0ef49b6aa8d056021e85 0 58 639 582 2022-02-11T09:31:16Z Admin 1 wikitext text/x-wiki == Keyboard == We have based our keyboard development following the Open Sourced [https://github.com/adereth/dactyl-keyboard Parameterized ergonomic keyboard] done by Matt Adereth and modified for our development by the Balthazar team. [https://github.com/g1smo/balthazar_dactyl Here] you can find our detailed documentation on a current modification and [https://github.com/g1smo/balthazar_qmk_firmware here] QMK firmware that we use in this development. Below you can see our modifications and although this design is currently divided into left and right we will merge this into a single keyboard controller for our laptop. === Dev PCB === <gallery> File:Pcb left.png |thumb| File:Pcb right.png|thumb| File:Dm keyboard left wire diagram.png|thumb| File:Dm keyboard right wire diagram.png|thumb| </gallery> === New keyboard PCB has been developed and adopted to Balthazar dimensions === <gallery> File:Pcb-keyboard-proto05.png|thumb|top File:Pcb-keyboard-proto06.png|thumb|bottom </gallery> Details on a new Keyboard module Features: • ISO standard keyboard layout • an ergonomic design • minimally (1/10th ) reduced keyboard size • silicone rubber waterproof overall keys blanket • microcontroller shared between keyboard, charger, safety control, and a touchpad PS2 to USB The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. Keyboard PCB has some dimensions already defined by the LCD's dimensions of 13.3 inches in diagonal: 290mm x 180mm. The width is the most determining factor for the keys raster, which is about 17mm – instead of the regular 19mm. The keys have some ergonomic solution that gives some additional design touch. The keyboard switches are important but are for now very typical low-cost membrane switches. A little better solution is the softer (silicone) – but still membrane – switches (not much love for the higher quality Cherry buttons). The idea is to have a waterproof (silicone) layer over the whole board. The board can then already act as a top cover. The feel of silicone rubber is preferred to that of natural rubber. Keyboard Schematics in: [[:File:BalthazarKeyboardSchematic02.pdf|.PDF]] Bill of materials (BoM) in: [[:File:BalthazarKeyboard-Bill.ods|.ODS]] PCB is ready for prototyping as KiCad files are available at our [https://github.com/balthazar-space Github] pages. Those will be regularly updated as schematics and PCBs are continuously improved and optimized. <gallery> File:Pcb-keyboard-proto03.png|top File:Pcb-keyboard-proto07.png|side File:Pcb-keyboard-proto04.png|bottom </gallery> === Prototype PCB === In early November 2020, we have received prototypes of keyboard PCBs, ready for implementing and connecting it to the other modules and for the correct dimensioning of a case and adjoining the screen. Here are the photos of a prototype, also with a 13.3" screen. <gallery> File:Key schem.png|thumb|with the schematic File:Key scr1.png|thumb|with the screen File:Key balt2cl.png|thumb|close-up with logo </gallery> Here it is with the key modules soldered on a keyboard prototype PCB, also with the controller chip and a micro USB. <gallery> File:Key solderedon.png|thumb|with the keys soldered on File:Key back.png|thumb|back side with a controller File:Keybackclup.png|thumb|controller close-up File:Key keyonclup.png|thumb|key modules close-up </gallery> Go to: [[I/O_USB|I/O hub]] or [[Power_Supply|Power Supply]] 92a6587a7b21199fe43011d909ead6b3a2bb197e 0 45 640 576 2022-02-11T10:33:26Z Admin 1 wikitext text/x-wiki The mission of '''Balthazar''' is to enable and educate end-users to be private, safe, and careful with their private, school's or a company's data. In today’s internet age we need to know how to handle and use encryption for our data protection, privacy, and overall security. Also, additional physical safety features such as hardwired switches and a quickly removable hard drive and peripherals are a necessity. Its open architecture runs a fully open-source software stack, a derivative of '''Debian GNU/Linux''' free of proprietary hardware drivers and other closed source software. This makes a large software library instantly available and provides regular security updates. It can also be used as a base for “custom OS” or even UI environment, but that should not be mandatory.<br> We are: # To design open, secure, inexpensive, and innovative hardware while combining it with the usage of already existing GNU/FOSS tools and applications right off the shelf. # To lead by example and gently lead other hardware manufacturers to become fully open towards GNU/FOSS including opening drivers' documentation, as well as abandoning in the developing process proprietary closed hardware architectures. # To support and enable low-income communities and individuals all over the planet to engage in protecting their privacy, freedoms, and rights on and within internet communication. # To make computing more sustainable and reach an eco-friendly footprint. # To make a modular and granulated product that can be configured and upgraded at an affordable price. You own it – you have the right to repair and upgrade it yourself. # To create an ecosystem that promotes RISC-V and ISA-based secure computing. # To position it as an educational platform, as well as an advanced computing device where its users of all ages will feel secure, safe, and comfortable using it. # To improve a paradigm in a mobile computing approach, while inspiring users to help create a new generation internet as a fundamental right to stay private, safe, and secure on- and off-line. 3b72092fb5315dd0420b10008db659e0eec34c6b 0 38 643 228 2022-03-29T10:42:17Z Admin 1 wikitext text/x-wiki <center>'''Send us a mail.'''</center><br> '''General''' inquiries, suggestions and requests - [mailto:info@balthazar.space info@balthazar.space]<br> 27dc119a4223d04ca6694c29134e3af1c3f76701 657 643 2022-05-18T14:13:04Z Admin 1 wikitext text/x-wiki <center>'''Send us a mail.'''</center><br> '''General''' inquiries, suggestions and requests - [mailto:info<at>balthazar.space info@balthazar.space]<br> 398208b72e5a768b2fce6a480e76f84fab2ce2d5 658 657 2022-05-18T14:13:35Z Admin 1 wikitext text/x-wiki <center>'''Send us a mail.'''</center><br> '''General''' inquiries, suggestions and requests - [mailto:info<at>balthazar.space]<br> f8deb744edb4f4603dfa04a8c4ed2852fe00b3f9 659 658 2022-05-18T14:14:05Z Admin 1 wikitext text/x-wiki <center>'''Send us a mail.'''</center><br> '''General''' inquiries, suggestions and requests - info<at>balthazar.space<br> 99c32f3b2bf325e89a275bf9a87d4a0f88e7bea4 0 126 645 2022-04-12T09:54:47Z Admin 1 Created page with "Unifying-PCB Unifying PCB expansion for Balthazar Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controll..." wikitext text/x-wiki Unifying-PCB Unifying PCB expansion for Balthazar Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. It is designed to accomodate ULX4M-CM4-HAT designed by Radiona.org using HDR 100 POS SMT board to board mezzanine connectors. dimensions: 60x90 mm placement: right back side of Balthazar casing 5581d0501a84a00a392c5726a073f54206272c37 648 645 2022-04-12T09:59:47Z Admin 1 wikitext text/x-wiki Unifying-PCB ==Unifying PCB expansion for Balthazar== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. It is designed to accomodate ULX4M-CM4-HAT designed by Radiona.org using HDR 100 POS SMT board to board mezzanine connectors. dimensions: 60x90 mm placement: right back side of Balthazar casing <gallery> File:Balthazar-CM4IO-img top.png |thumb| File:Balthazar-CM4IO-img bottom.png |thumb| </gallery> 29d747fcaedbf4a6801e3518275653a97906411e 649 648 2022-04-12T10:00:45Z Admin 1 /* Unifying PCB expansion for Balthazar */ wikitext text/x-wiki Unifying-PCB ==Unifying - PCB expansion for Balthazar== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. It is designed to accomodate ULX4M-CM4-HAT designed by Radiona.org using HDR 100 POS SMT board to board mezzanine connectors. dimensions: 60x90 mm placement: right back side of Balthazar casing <gallery> File:Balthazar-CM4IO-img top.png |thumb| File:Balthazar-CM4IO-img bottom.png |thumb| </gallery> 190bcf3cb5d677bf49d23fca026203841b973285 650 649 2022-04-12T10:01:36Z Admin 1 /* Unifying - PCB expansion for Balthazar */ wikitext text/x-wiki Unifying-PCB ==Unifying - PCB expansion for Balthazar== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. It is designed to accomodate ULX4M-CM4-HAT designed by [https://radiona.org Radiona.org] using HDR 100 POS SMT board to board mezzanine connectors. dimensions: 60x90 mm placement: right back side of Balthazar casing <gallery> File:Balthazar-CM4IO-img top.png |thumb| File:Balthazar-CM4IO-img bottom.png |thumb| </gallery> f192f7bbc85ef6ebb2312e412d4664775d0586b1 6 127 646 2022-04-12T09:55:36Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 128 647 2022-04-12T09:57:16Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 129 654 2022-05-16T10:53:12Z Admin 1 Created page with "== Documentation == 1. Module BalthazarPSU is a combined battery charger, buck-boost coverter and stereo power amplifier. 2. Module BalthazarKeyboard is a simplified a bit e..." wikitext text/x-wiki == Documentation == 1. Module BalthazarPSU is a combined battery charger, buck-boost coverter and stereo power amplifier. 2. Module BalthazarKeyboard is a simplified a bit ergonomic computer keyboard with "diy" approch. in the two versions. The second iteration of the updated keyboard is having some more geometric consistency. 3. Module BalthazarIO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audiocard. 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. e52b5ab7dc4eff0414b184046e7c2dda4c1cc243 655 654 2022-05-16T10:54:09Z Admin 1 /* Documentation */ wikitext text/x-wiki == Documentation and instruction manuals== 1. Module BalthazarPSU is a combined battery charger, buck-boost coverter and stereo power amplifier. 2. Module BalthazarKeyboard is a simplified a bit ergonomic computer keyboard with "diy" approch. in the two versions. The second iteration of the updated keyboard is having some more geometric consistency. 3. Module BalthazarIO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audiocard. 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. 52c4c19add3553113b9bd85dba1315d5ec9b7c7a 660 655 2022-06-02T14:44:19Z Admin 1 /* Documentation and instruction manuals */ wikitext text/x-wiki == Documentation and instruction manuals== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with "diy" approach. in the two versions. The second iteration of the updated keyboard is having some more geometric consistency. 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. a8205c32b802ee79b044c1c43ec0e2f12230cde8 0 46 661 651 2022-06-06T12:58:02Z Admin 1 wikitext text/x-wiki == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real "alpha" working prototype, but mostly all our PCBs and other adjoining elements will be ready. ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 5e1a112110a4d466facae919ef680b6f283d4805 705 661 2022-06-15T04:38:21Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real "alpha" working prototype, but mostly all our PCBs and other adjoining elements will be ready. ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. d9a219484e43a9fde0bbf0560e6d92987bea991a 0 129 662 660 2022-06-08T09:00:37Z Admin 1 wikitext text/x-wiki == Documentation and instruction manuals== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), web cam and optional audio card. 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. 3b96f3f4c3e83e537dcea7d4f39b05c4a2809dd0 680 662 2022-06-09T12:38:26Z Admin 1 wikitext text/x-wiki == Documentation and instruction manuals== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. [[File:PSU.png|center|PSU]] 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), web cam and optional audio card. [[File:IO.png|center|Input-Output]] 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying.png|center|Unifying Board]] e3e5b2bb60b36d120a468adc645755c9fb6d2eef 682 680 2022-06-09T12:52:34Z Admin 1 wikitext text/x-wiki = Documentation and instruction manuals = == Balthazar Modules set == [[File:Bset.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. [[File:PSU.png|center|PSU]] 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), web cam and optional audio card. [[File:IO.png|center|Input-Output]] 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying.png|center|Unifying Board]] 04a86eacc3805a6a122515fb5ed1c6bdc4feb083 683 682 2022-06-09T12:54:05Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == [[File:Bset.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. [[File:PSU.png|center|PSU]] 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), web cam and optional audio card. [[File:IO.png|center|Input-Output]] 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying.png|center|Unifying Board]] a28a2de7d1537f52bcaa269cb1365c4f2e5913d6 687 683 2022-06-09T16:15:12Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == [[File:Bset.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. [[File:PSU.png|center|PSU]] 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), web cam and optional audio card. [[File:IO.png|center|Input-Output]] 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] e32d56031302ff35d079ed2a4dbcb3692767b498 688 687 2022-06-10T13:43:36Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == [[File:Bset.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. [[File:PSU.png|center|PSU]] 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] 85d6150ef31bd1db662e1668ca5fb4e308d8ef95 689 688 2022-06-10T13:44:39Z Admin 1 /* Description of the Balthazar modules */ wikitext text/x-wiki == Balthazar Modules set == [[File:Bset.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. [[File:PSU.png|center|PSU]] 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] 888e75761765790d8decd7c77e303eba4f342ee1 690 689 2022-06-10T13:45:51Z Admin 1 /* Description of the Balthazar modules */ wikitext text/x-wiki == Balthazar Modules set == [[File:Bset.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via USB. [[File:PSU.png|center|PSU]] 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] 1aa888b1dfa59763f14801211a3cf328dbaabb34 691 690 2022-06-10T14:02:05Z Admin 1 /* Balthazar Modules set */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules top view. Below is a description of each module. [[File:Bset.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via USB. [[File:PSU.png|center|PSU]] 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] 315db4514c07f1e5311ec475a8a2b8a4fd02da4b 693 691 2022-06-10T15:53:30Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules top view. Below is a description of each module. [[File:Bset1.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via USB. [[File:PSU.png|center|PSU]] 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] 31cce1417acbc9468b70ff7b07611909e9316834 695 693 2022-06-11T09:19:19Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules top view. Below is a description of each module. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via USB. [[File:PSU.png|center|PSU]] 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] 693c67480a7b1e45d6f7e76258a800fb71fa04a9 696 695 2022-06-11T09:20:07Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module Balthazar PSU is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via USB. [[File:PSU.png|center|PSU]] 2. Module Balthazar Keyboard is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module Balthazar IO is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. Unifying PCB is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] 1817502401a19aee0538f8d14766e04258a455d3 6 130 663 2022-06-08T11:23:50Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 1 664 656 2022-06-08T11:25:03Z Admin 1 wikitext text/x-wiki __NOTOC__ == <center><strong>a Personal Computing Device</strong></center> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Z2.png|center|Artist's conception]] '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Documentation]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> 1e55b65faad1f726b894d8cdec72216ec257cdc3 668 664 2022-06-08T11:45:56Z Admin 1 wikitext text/x-wiki __NOTOC__ == <center><strong>a Personal Computing Device</strong></center> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Z2.png|center|Artist's conception]] <gallery> File:Z3.png|thumb| File:Z4.png|thumb| File:Z6.png|thumb| </gallery> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Documentation]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> d4171163b64e8369b64ec116dbc6ec4d0590d135 669 668 2022-06-08T11:53:06Z Admin 1 wikitext text/x-wiki __NOTOC__ == <center><strong>a Personal Computing Device</strong></center> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Z2.png|center|Artist's conception]] <gallery mode=packed> File:Z3.png|thumb| File:Z4.png|thumb| File:Z6.png|thumb| </gallery> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Documentation]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> 1408e5c293bae32241b8abd8551e6ba392286ea3 670 669 2022-06-08T12:09:06Z Admin 1 wikitext text/x-wiki __NOTOC__ == <center><strong>a Personal Computing Device</strong></center> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:Z2.png|center|prototype]] <gallery mode=packed> File:Z3.png|thumb| File:Z4.png|thumb| File:Z6.png|thumb| </gallery> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Documentation]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> e965f913313104abdb5b222a6579f02e8d26c80e 675 670 2022-06-08T12:42:40Z Admin 1 wikitext text/x-wiki __NOTOC__ == <center><strong>a Personal Computing Device</strong></center> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:P3.resized.png|center|prototype]] <gallery mode=packed> File:P1.resized.png|thumb| File:P2.resized.png|thumb| File:P4.resized.png|thumb| </gallery> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Documentation]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> 41d8fd8ea1210bde6a505792d6058ccd91f40f87 684 675 2022-06-09T14:16:42Z Admin 1 wikitext text/x-wiki __NOTOC__ == <center><strong>a Personal Computing Device</strong></center> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:P3.resized.png|center|prototype]] <gallery mode=packed> File:P1.resized.png|thumb| File:P2.resized.png|thumb| File:P4.resized.png|thumb| </gallery> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture that runs on '''[https://www.linux.org Linux OS]''' with added co-processing power based on FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Documentation]] and [[Instruction Manual]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> 4c419a53ce91c61b26281af65c449789fe4a48bc 6 131 665 2022-06-08T11:27:08Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 132 666 2022-06-08T11:28:07Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 133 667 2022-06-08T11:28:45Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 134 671 2022-06-08T12:36:52Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 135 672 2022-06-08T12:37:29Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 136 673 2022-06-08T12:38:09Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 137 674 2022-06-08T12:39:25Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 138 676 2022-06-09T12:31:18Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 139 677 2022-06-09T12:34:18Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 140 678 2022-06-09T12:35:17Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 141 679 2022-06-09T12:36:43Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 142 681 2022-06-09T12:44:43Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 143 685 2022-06-09T14:17:41Z Admin 1 Created page with "== Balthazar Instruction Manual ==" wikitext text/x-wiki == Balthazar Instruction Manual == ff95022a7ec7d0575ef8513a9bf5a2224f04b709 697 685 2022-06-13T11:39:16Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar is put together. c407d5129e4a0144dca50606b255b69b6b9ca804 698 697 2022-06-14T19:50:30Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar is put together. <iframe width="560" height="315" src="https://www.youtube.com/embed/0ZTawtxvtcQ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> 617bea9ea74d9a305f154e58e89f75e2ac578818 699 698 2022-06-14T19:54:05Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar is put together. c407d5129e4a0144dca50606b255b69b6b9ca804 702 699 2022-06-14T20:17:02Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar is put together. {{#evt: service=youtube |id=https://www.youtube.com/watch?v=0ZTawtxvtcQ |alignment=right }} 217e5cbe25da78591f568824f17dc57f59c0ba77 703 702 2022-06-14T20:17:16Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar is put together. {{#evt: service=youtube |id=https://www.youtube.com/watch?v=0ZTawtxvtcQ |alignment=left }} c4393919baed22699e7b75207b79d49dd8283b70 704 703 2022-06-14T20:18:34Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar is put together. {{#evt: service=youtube |id=https://www.youtube.com/watch?v=0ZTawtxvtcQ |alignment=center }} 050ca1c7acac722916d1239831ef0976f9e915e8 706 704 2022-06-15T06:11:13Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar modules are connected. {{#evt: service=youtube |id=https://www.youtube.com/watch?v=0ZTawtxvtcQ |alignment=center }} 578a59664559b51662676d0ef9a4f8dcd812f526 707 706 2022-06-15T12:04:26Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar modules are connected. {{#evt: service=youtube |id=https://youtu.be/b1_3ODmtGrg |alignment=center }} 3f8dbc9822f1d24f1321cf5efd64a56a624396c8 708 707 2022-06-15T12:06:11Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar modules and components are connected. Part 1. {{#evt: service=youtube |id=https://youtu.be/b1_3ODmtGrg |alignment=center }} 8ec7c4d82de860791bfaf9d8675263d23cfdeaad 709 708 2022-06-16T10:16:53Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar modules and components are connected. Part 1. {{#evt: service=youtube |id=https://youtu.be/b1_3ODmtGrg |alignment=center }} This is the part two video of Balthazar modules being assembled in the case. {{#evt: service=youtube |id=https://youtu.be/OXpZlAP7rX8 |alignment=center }} c4cdc344152f7826aa8e078df2141590eafd0dee 710 709 2022-06-16T11:09:57Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar modules and components are connected and how it fits into the case. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} 2d15775032fe7a155f399129ad7cc42942171085 6 144 686 2022-06-09T16:13:56Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 145 692 2022-06-10T15:52:26Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 146 694 2022-06-11T09:18:41Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 8 24 700 416 2022-06-14T20:01:13Z Admin 1 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Features|Features & Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** Documentation|Documentation ** Instruction Manual|Instruction Manual ** News|News ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact ** https://github.com/balthazar-space|GitHub page * Wiki ** Special:RecentChanges|Recent Changes ** Special:AllPages|All Pages ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages * SEARCH * TOOLBOX * LANGUAGES f6683df07289a9ae1146fc854db51dc699765fe3 701 700 2022-06-14T20:10:39Z Admin 1 wikitext text/x-wiki * About ** Balthazar|Introduction ** Goals|Goals ** Features|Features & Specifications ** Aperture Operating Environment|Operating Environment ** User Experience|User Experience ** Education|Education ** Documentation|Documentation ** Instruction Manual|Instruction Manual ** News|News ** FAQ|FAQ ** Links|Links ** Glossary|Glossary ** Contact|Contact ** https://github.com/balthazar-space|GitHub page * Wiki ** Special:RecentChanges|Recent Changes ** Special:AllPages|All Pages ** Special:ListFiles|List Files ** Special:Upload|Upload a File ** Special:SpecialPages|Special Pages ** Special:Version|About * SEARCH * TOOLBOX * LANGUAGES f80dd5e22eb210393e6856f275f30f0868886d54 0 143 711 710 2022-06-16T11:11:11Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar modules and components are connected and how it all fits into the case. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} 7da50354109d293914842f18b6b30bd9b641c0e6 712 711 2022-06-16T11:29:38Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar modules and components are connected and how it all fits into the case. {{#evt: service=youtube |id=https://youtu.be/OXpZlAP7rX8 |alignment=center }} a517d3f3cdd571bda0136fe43d7cfc6a3e9a8b19 713 712 2022-06-16T11:31:35Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar modules and components are connected and how it all fits into the case. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} 7da50354109d293914842f18b6b30bd9b641c0e6 735 713 2022-06-17T11:03:03Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar modules and components are connected and how it all fits into the case. Main modules are connected via a flat and short USB cable, while 2-wire cable connects to a speaker. 3-wire cables are used to connect to the battery pack. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} e309e1d5ce7b601ae068b3a3b254dc86840415ca 736 735 2022-06-17T11:12:34Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is shown how Balthazar modules and components are connected and how it all fits into the case. Main modules are connected via a flat and short USB cable, while 2-wire cable connects to a speaker. 3-wire cables are used to connect to the battery pack. All the elements are placed into the casing and screwed to a chassis. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} 9adf30b1ada82d434139696dba23da6eb57a1ec8 737 736 2022-06-17T11:20:07Z Admin 1 /* Balthazar Instruction Manual */ wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable, while 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB. The touchpad and small screen are connected to a IC2 that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis. Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} 84cb741ef8aad6de302fab6a7cce2427e8034c4e 740 737 2022-06-17T11:40:29Z Admin 1 /* Balthazar Instruction Manual */ wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable, while 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB. The touchpad and small screen are connected to a I2C that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis. Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} 912b2483b97316736b3b8d892ccef8de8b8d8d19 741 740 2022-06-17T11:42:46Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable, while 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB. The touchpad and small screen are connected to a I2C that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis (in development). Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} db16f1ed9d1ee95c8602cf3271f1eb8b4f1ef57a 742 741 2022-06-17T11:45:17Z Admin 1 /* Balthazar Instruction Manual */ wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable, while the flat 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB. The touchpad and small screen are connected to a I2C that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis (in development). Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} d8a958b4dd9bb633ac92b52c8c6b1a1076636c8d 759 742 2022-06-20T12:23:35Z Admin 1 /* Balthazar Instruction Manual */ wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable Type A or a combined, while the flat 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB. The touchpad and small screen are connected to a I2C that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis (in development). Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} 63fecc49b36f7d398be659bbc4d579330bf4c211 6 147 714 2022-06-17T10:03:12Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 148 715 2022-06-17T10:04:20Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 149 716 2022-06-17T10:05:19Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 46 717 705 2022-06-17T10:11:26Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real "alpha" working prototype, but mostly all our PCBs and other adjoining elements will be ready. And here are PCB modules that we received, Unifying board, keyboard and PSU. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. a08398d8e8af0739c2023caba1182971b58ceeb8 718 717 2022-06-17T10:13:03Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real "alpha" working prototype, but mostly all our PCBs and other adjoining elements will be ready. And here are PCB modules that we received, Unifying board, keyboard and PSU and are produced. Those are ready to be built and connected to a working order. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 297370f0d3d87c137f0433d1b608a911e6487d6d 719 718 2022-06-17T10:14:00Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real "alpha" working prototype, but mostly all our PCBs and other adjoining elements will be ready. And here are PCB modules that we received, Unifying board, keyboard and PSU and are produced. Those are ready to be built and connected to a working order. MOre pictures to come soon. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 551af990e17f8b102d6c820f54f97b3922290b99 724 719 2022-06-17T10:31:15Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real "alpha" working prototype, but mostly all our PCBs and other adjoining elements will be ready. And here are PCB modules that we received, Unifying board, keyboard and PSU and are produced. Those are ready to be built and connected to a working order. More pictures of interconnected PCBs to come soon. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 72fae31e97437379e38c4b91dbaad2720dd9f5bf 725 724 2022-06-17T10:32:06Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real "alpha" working prototype, but mostly all our PCBs and other adjoining elements will be ready. And here are PCB modules that we received, Unifying board, keyboard and PSU and are produced. Those are ready to be built and connected to a working state. More pictures of interconnected PCBs to come real soon. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 7ad7a53a3101d6481170cf952ead66338cca235b 726 725 2022-06-17T10:41:58Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real "alpha" working prototype, but mostly all our PCBs and other adjoining elements are ready. And here are PCB modules that we received, Unifying board, keyboard and PSU and are produced. Those are ready to be built and connected to a working state. More pictures of interconnected PCBs to come real soon. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 75fd6ea68516c1f7fb48209ca4fea4fae037e89e 743 726 2022-06-17T12:08:57Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. And here are PCB modules that we received, Unifying board, keyboard and PSU and are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. More pictures of interconnected PCBs to come real soon. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. cf60c60977664d97038985294b0ed1d43eccbdca 744 743 2022-06-17T12:28:26Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. More pictures of interconnected PCBs to come real soon. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 8a39817fc53115263d5e40068fa15c6e7c971481 748 744 2022-06-17T13:57:20Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are tests of Balthazar's modules, screen, and a keyboard working with RP3. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt work8.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 3b24cc5dc47c9d6326d63e5d85ca69557a7a348d 749 748 2022-06-17T13:58:04Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are tests of Balthazar's modules, screen, and a keyboard working with RP3. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt work8.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 7f6c630c3734db07cc49b2b6c8c4950eddf82449 751 749 2022-06-17T14:04:07Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are tests of Balthazar's modules, screen, and a keyboard working with RP3. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt work8.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 3949be6bf9b83dd785077c06be8b8a87e59e77ad 752 751 2022-06-17T14:13:38Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are tests of Balthazar's modules, screen, and a keyboard working with RP3. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 1856764d92cea1d2d238b0a4e6a14cadbda9b30e 753 752 2022-06-17T14:41:18Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 121b2eca8d1b5989fe3614308406cc038a4be7a9 754 753 2022-06-17T18:30:15Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final case design, also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with new design and images of the case. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. b4aaaa6d524b88b47a9cd78388bdc6b0f7bb5020 755 754 2022-06-20T06:14:49Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating documentation and instruction manual assembly. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with new design and images of the case. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 391689fa6ad7bce20fe0a4dbf8a897591f5ac374 756 755 2022-06-20T06:16:04Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with new design and images of the case. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 7ac0875a76767a4d984508a39e23bff61a425ff6 757 756 2022-06-20T06:18:01Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the case. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 587a809bdcc3c0b8e1ed594db8e4673493e4ef81 0 129 720 696 2022-06-17T10:18:58Z Admin 1 /* Description of the Balthazar modules */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via USB. [[File:PSU.png|center|PSU]] 2. Module [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] 7b09a102ec5001d33225fc7f59829566dd0eede4 721 720 2022-06-17T10:23:37Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables to a power supply PCB that also charges the batteries and controls the voltage. Power supply would need an external USB-C charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via USB. [[File:PSU.png|center|PSU]] 2. Module [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] 1c6af51afa0e055d488b8a949c5da2e61db66a83 727 721 2022-06-17T10:44:03Z Admin 1 /* Balthazar Modules set */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via USB. [[File:PSU.png|center|PSU]] 2. Module [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] 71d439acfed1385ebd8a8f8a3f263fdb9fff06e7 728 727 2022-06-17T10:46:16Z Admin 1 /* Description of the Balthazar modules */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. [[File:PSU.png|center|PSU]] 2. Module [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] bf743e09a44f25b998b71ecf923509305e64d1bd 729 728 2022-06-17T10:50:30Z Admin 1 /* Description of the Balthazar modules */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. Technical description: Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] 2. Module [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] ed869b6ca5ca062541671c6304834f1954243654 730 729 2022-06-17T10:50:44Z Admin 1 /* Description of the Balthazar modules */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== 1. Module [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. Technical description: Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] 2. Module [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] 3. Module [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] 4. [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] 5e523852ff423d2c77d84b73df1d5ea5b5e0fc33 731 730 2022-06-17T10:52:16Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. [[File:Unifying1.png|center|Unifying Board]] e2742d3658a1f76c18b220675f16ade06e8d6f1e 732 731 2022-06-17T10:55:44Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. [[File:Keyboard.png|center|Keyboard]] '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] 3b8b3b4b9dba32bcd8e0fb6f201296d9c33babf6 733 732 2022-06-17T10:56:28Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] 88739e0c1eb303ea362447556b492bbaa425dba4 734 733 2022-06-17T10:59:36Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] c1e1a40f3077e0ae1a04acea841a630d8b9da813 738 734 2022-06-17T11:37:51Z Admin 1 /* Balthazar Modules set */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] de26335d96f255a52cb9c07fff8509169ed9dcf9 739 738 2022-06-17T11:39:57Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] 97ef2d6c1a60c7710ad48bee3c83a75072034ca8 758 739 2022-06-20T12:21:16Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] 9aba421d219b8ca7fd08362c26e98f004ad9e5b1 760 758 2022-06-20T13:40:32Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. BoM for each module is respective folder on our [https://github.com/balthazar-space Github page]. 132a949c922cc6f4f641943391c29208eb9bc0a2 6 150 722 2022-06-17T10:28:54Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 151 723 2022-06-17T10:30:41Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 152 745 2022-06-17T13:48:21Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 153 746 2022-06-17T13:52:31Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 154 747 2022-06-17T13:54:09Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 155 750 2022-06-17T14:03:24Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 129 761 760 2022-06-20T13:43:08Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. BoM for each module is respective folder on our [https://github.com/balthazar-space Github page]. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> f225c9816d5fd55819447b3c75648c251ca03a30 762 761 2022-06-20T14:28:54Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. BoM for each module is in respective folder on our [https://github.com/balthazar-space Github page]. <gallery> File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> 1e88179d9a55a800e6b7ad1a3acd8e9cdf9b9e3c 765 762 2022-06-21T12:55:17Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. BoM for each module is in respective folder on our [https://github.com/balthazar-space Github page]. Production of the keyboard is shown. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> b595156d2c019cc1c7410055892b7525df450439 766 765 2022-06-21T13:16:23Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. BoM for each module is in respective folder on our [https://github.com/balthazar-space Github page]. Production and a module of the keyboard is shown below. <gallery> File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| </gallery> Production of all the modules below will be gradually shown below. <gallery> File:Balt unify.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> 008d8b28f8c6dbb4fbeb327a90a84f5a501cc213 767 766 2022-06-21T13:20:52Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. BoM for each module is in respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard is shown below. <gallery> File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| </gallery> Production of all the modules below will be gradually shown below. <gallery> File:Balt unify.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> 5f594fc17210b59fe72a4799bfe51d108eba27d4 768 767 2022-06-21T16:02:33Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. BoM for each module is in respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard is shown below. For the keyboard module, an interactive iBoM (interactive Bill of materials) is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/bom/ibom.html Balthazar Keyboard iBoM] can be found on our [https://github.com/balthazar-space Github page.] <gallery> File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| </gallery> Production of all the modules below will be gradually shown below. <gallery> File:Balt unify.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> 3238a6c1dbeb93ac87eaf9bd30a2388b7e1b1cff 769 768 2022-06-21T16:04:28Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. BoM for each module is in respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard is shown below. For the keyboard module, an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/bom/ibom.html Balthazar Keyboard iBoM] can be found on our [https://github.com/balthazar-space Github page.] <gallery> File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| </gallery> Production of all the modules below will be gradually shown below. <gallery> File:Balt unify.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> 966fa9baeb93f4dbaeecc1d5a8bb8e41e70361d5 770 769 2022-06-22T07:44:04Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. BoM for each module is in respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/bom/ibom.html Balthazar Keyboard iBoM] can be found on our [https://github.com/balthazar-space Github page.] <gallery> File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| </gallery> Production of all the modules below will be gradually shown below. <gallery> File:Balt unify.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> f903ef0d25a8b36bf65c03f513eb46008d2b2fa5 772 770 2022-06-22T10:56:17Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/bom/ibom.html Balthazar Keyboard iBoM] can be found on our [https://github.com/balthazar-space Github page.] <gallery> File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| </gallery> Production of all the modules below will be gradually shown below. <gallery> File:Balt unify.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> 78bbc7f490e3f536bf90ceea3ae2a6b5fd2ee1f0 776 772 2022-06-29T14:21:37Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/bom/ibom.html Balthazar Keyboard iBoM] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for our keyboard. <gallery> File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Kitspace.png|thumb| </gallery> Production of all the modules below will be gradually shown below. <gallery> File:Balt unify.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> f1458b4713c6bbe7a269f29aef09d428fc9d2eea 777 776 2022-06-29T14:25:14Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. ==== Keyboard ==== Production start and a process with a PCB module of the keyboard is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/bom/ibom.html Balthazar Keyboard iBoM] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for our keyboard. <gallery> File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Kitspace.png|thumb| </gallery> Production of all the modules below will be gradually shown below. <gallery> File:Balt unify.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> 204c6aa5bc875885b97e4c7a347b48e455cfa165 788 777 2022-09-13T10:43:49Z Admin 1 /* Keyboard */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. ==== Keyboard ==== Production start and a process with a PCB module of the keyboard is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/bom/ibom.html Balthazar Keyboard iBoM] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for our keyboard. <gallery> File:KeyBoard3 sourced.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Kitspace.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Production of all the modules below will be gradually shown below. <gallery> File:Balt unify.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> 2d598ce588d6784ae263fb992df088f9b9379c39 793 788 2022-09-13T10:54:39Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. ==== Balthazar Keyboard ==== Production start and a process with a PCB module of the keyboard is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/bom/ibom.html Balthazar Keyboard iBoM] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for our keyboard. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Production of all the modules below will be gradually shown below. <gallery> File:Balt unify.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| </gallery> e9e0a069110733a0d1ef13b48c2c079361b5307f 797 793 2022-09-13T11:50:25Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/bom/ibom.html Balthazar Keyboard iBoM] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for our keyboard. ==== Balthazar Keyboard ==== <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> ==== PSU I/O board ==== <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> a64defd16786d2bc65146555f57a409cd632929d 798 797 2022-09-13T11:57:29Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/bom/ibom.html Balthazar Keyboard iBoM] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for our keyboard. ==== Balthazar Keyboard ==== <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> ==== PSU I/O board ==== <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> 7bdbfb0eb26a462a09e0b38663760b000ff54eb5 799 798 2022-09-13T12:01:10Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard iBoM][https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for our keyboard. ==== Balthazar Keyboard ==== <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> ==== PSU I/O board ==== <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> fa9da777ead4a1cc8dea89058ef6a9ba2748250c 800 799 2022-09-13T12:02:04Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for our keyboard. ==== Balthazar Keyboard ==== <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> ==== PSU I/O board ==== <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> 7e36a648d77876eb0939445bc462c2b13dda7287 801 800 2022-09-13T12:03:08Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. ==== Balthazar Keyboard ==== <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> ==== PSU I/O board ==== <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> 97f60a4bb29b6506d5cfc7b32c1d19581a9a64bf 803 801 2022-09-21T11:25:05Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> ==== PSU I/O board ==== <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> 3e7141d78c855aae7a3950d3cb955fcc583b067e 804 803 2022-09-21T11:44:01Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} 285512c55dd1f56e832fb324d215fdf414881b94 805 804 2022-09-22T08:12:20Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Video of assembling the Balthazar Unifying Board. {{#evt: service=youtube |id=https://youtu.be/ygKlJUs1uTE |alignment=center }} ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} 64ad912031b3703f326acfa1380f6bb0b9572964 806 805 2022-09-22T08:58:54Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarKeyboard3/issues here]. ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Video of assembling the Balthazar Unifying Board. {{#evt: service=youtube |id=https://youtu.be/ygKlJUs1uTE |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/Unifying-PCB/issues here]. ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarPSU3/issues here]. 3010e8fcce75bcee280a0e78776ea74d2afc2621 6 156 763 2022-06-21T12:46:19Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 46 764 757 2022-06-21T12:47:41Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the case. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. a787fbce88239a1a9bc6c29042e56a1ba717f658 771 764 2022-06-22T10:55:02Z Admin 1 /* June 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the case. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 2f74bbf17bcbd3c91a0b37e38ec2cd93f692eada 774 771 2022-06-24T07:07:51Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 8903b3ab586248f84fa76beedf63a8a2c4b1a02d 778 774 2022-07-08T07:38:19Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. eaf30166f471230c70b4377e2328bf6926c397ce 779 778 2022-08-25T14:37:48Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==August 2022== There are modules being produced and tested during August and we will post the results. Also here some of the pictures when ready. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 0602b923b30fd35ef5233e767b88c74856dcdf57 783 779 2022-09-06T09:56:30Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| ==August 2022== There are modules being produced and tested during August and we will post the results. Also here some of the pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 4179d6b2f94a9e66010893c7c0566aeed547b869 784 783 2022-09-06T09:56:54Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also here some of the pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 2d946d8fb45118c62608ceedef8d8e787a6438fb 785 784 2022-09-06T09:58:22Z Admin 1 /* August 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 831820f0a2a32f3ae9b64b6e06ef5f9cb6a235a3 0 55 773 644 2022-06-23T08:19:20Z Admin 1 /* Case */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Software== Software depends on a System on a Module used. See more: [[Software]] 82b7ba2db80300c789fe11f8e8c35d1dfe11f759 809 773 2022-09-22T09:21:45Z Admin 1 wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Lithium - Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Battery implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|thumb File:Batt ch test12V.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] 746097c7e12679f55288bc4f3afce224820882ec 810 809 2022-09-22T09:22:24Z Admin 1 /* Battery */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Lithium - Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Battery implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|thumb File:Batt ch test12V.png|thumb </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] 15bb370a417d7d3d56c3c67a691b07ab5ed29fef 6 157 775 2022-06-29T14:19:02Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 158 780 2022-09-06T09:53:24Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 159 781 2022-09-06T09:54:35Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 160 782 2022-09-06T09:55:37Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 161 786 2022-09-13T10:39:08Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 162 787 2022-09-13T10:42:06Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 163 789 2022-09-13T10:49:02Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 164 790 2022-09-13T10:51:11Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 165 791 2022-09-13T10:52:53Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 166 792 2022-09-13T10:53:59Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 167 794 2022-09-13T11:39:22Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 168 795 2022-09-13T11:41:40Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 169 796 2022-09-13T11:47:17Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 143 802 759 2022-09-21T10:37:52Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable Type A or a combined, while the flat 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB. The touchpad and small screen are connected to a I2C that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis (in development). Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} Internal connections are also available for camera adoptions, as it is shown on the video below. {{#evt: service=youtube |id=https://youtu.be/Nm6NnHadsa0 |alignment=center }} 88acc8e1c115325cfbae1acafcf6a37182479d02 6 170 807 2022-09-22T09:16:40Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 171 808 2022-09-22T09:17:49Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 55 811 810 2022-09-22T09:22:57Z Admin 1 /* Battery */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Lithium - Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Battery implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] 8bd93b0a648d624fea430c8296fb32f5c344b4f3 812 811 2022-09-22T09:24:29Z Admin 1 /* Battery */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Battery implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] 6f9c586e1bbb0370d59a488429f99c5bb2b2981e 815 812 2022-09-22T10:05:00Z Admin 1 wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Battery implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] db4cc64986308648794f16b6b5d42d6ebfebe822 819 815 2022-09-22T11:57:59Z Admin 1 /* Display Controller and a screen panel */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Test screen on Unifying Board with CM4 module working. <gallery> File:DSI1 balt.screen.png </gallery> ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Battery implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] e9e3a85ac12ba4c1165aee8a7bd94e6f31b81b05 820 819 2022-09-22T12:01:25Z Admin 1 /* Display Controller and a screen panel */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Test screen on '''Unifying Board''' with CM4 module working. <gallery> File:DSI1 balt.screen.png </gallery> ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Battery implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] f53c5b956f36686afef145b980e27a53c3ac657d 822 820 2022-09-22T12:05:48Z Admin 1 /* Display Controller and a screen panel */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Test screen on '''Unifying Board''' with CM4 module working. Also works in a full configuration. <gallery> File:DSI1 balt.screen.png File:MIPI display.png </gallery> ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Battery implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] 13f980c277f9c7fd22a81e5358af413d66845653 825 822 2022-09-28T08:33:04Z Admin 1 /* Display Controller and a screen panel */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Test screen on '''Unifying Board''' with CM4 module working. Also works in a full configuration. <gallery> File:DSI1 balt.screen.png File:MIPI display.png File:DSI1 balt cabling.png File:DSI1 balt fix.png </gallery> ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== See more: [[Keyboard]] ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Battery implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] 9d4c294f12990d901d802cfa9f24caaa61c6b874 838 825 2022-10-01T09:19:49Z Admin 1 /* Keyboard and Touch-pad */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Test screen on '''Unifying Board''' with CM4 module working. Also works in a full configuration. <gallery> File:DSI1 balt.screen.png File:MIPI display.png File:DSI1 balt cabling.png File:DSI1 balt fix.png </gallery> ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== For specific Balthazar keyboard, see: [[Keyboard]] We develop add-on PCB to accommodate well known and basically industry standard keyboard as it is found in ThinkPad x2XX series. This will enable users to use an inexpensive replacement keyboard should they have need for it. Casing design envisage accommodating frame to fix additional keyboard in place. Touchpad on specific Balthazar's keyboard is connected via I2C bus. ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Battery implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] 2c5fe0bcbb87302134f1c0329366c3a1c81d3fe8 839 838 2022-10-01T09:22:54Z Admin 1 /* Battery */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Test screen on '''Unifying Board''' with CM4 module working. Also works in a full configuration. <gallery> File:DSI1 balt.screen.png File:MIPI display.png File:DSI1 balt cabling.png File:DSI1 balt fix.png </gallery> ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== For specific Balthazar keyboard, see: [[Keyboard]] We develop add-on PCB to accommodate well known and basically industry standard keyboard as it is found in ThinkPad x2XX series. This will enable users to use an inexpensive replacement keyboard should they have need for it. Casing design envisage accommodating frame to fix additional keyboard in place. Touchpad on specific Balthazar's keyboard is connected via I2C bus. ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Up to 6 batteries are proposed to power Balthazar, however an additional Baterry Control Monitor should be implemented or as separate unit. Also research into other battery systems is done. Current battery candidate implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] 7ec1ddfd85c3a7b70ea1676d5ee4e01f23ea8658 0 143 813 802 2022-09-22T09:28:31Z Admin 1 /* Balthazar Instruction Manual */ wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable Type A or a combined, while the flat 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB or a flat cable. The touchpad and small screen are connected to a I2C that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis (in development). Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} Internal connections are also available for camera adoptions, as it is shown on the video below. {{#evt: service=youtube |id=https://youtu.be/Nm6NnHadsa0 |alignment=center }} '''GPIO''' cable we implement is ribbon cable with IDC connectors; 40x28AWG; Cable ph: 1.27mm. e7efabac6a3cd5f4b459b328301de51993f96ead 817 813 2022-09-22T10:10:12Z Admin 1 /* Balthazar Instruction Manual */ wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable Type A or a combined, while the flat 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB or a flat cable. The touchpad and small screen are connected to a I2C that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis (in development). Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} Internal connections are also available for camera adoptions, as it is shown on the video below. {{#evt: service=youtube |id=https://youtu.be/Nm6NnHadsa0 |alignment=center }} '''GPIO''' cable we implement is ribbon cable with IDC connectors; 40x28AWG; Cable ph: 1.27mm. <gallery> File:Gpio cable.png </gallery> b76c61802e8add20b6563f0753922f3e78656ff5 828 817 2022-09-28T11:02:09Z Admin 1 /* Balthazar Instruction Manual */ wikitext text/x-wiki == Balthazar Instruction Manual == In this video it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable Type A or a combined, while the flat 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB or a flat cable. The touchpad and small screen are connected to a I2C that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis (in development). Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} Internal connections are also available for camera adoptions, as it is shown on the video below. {{#evt: service=youtube |id=https://youtu.be/Nm6NnHadsa0 |alignment=center }} '''GPIO''' cable we implement is ribbon cable with IDC connectors; 40x28AWG; Cable ph: 1.27mm. <gallery> File:Gpio cable.png </gallery> Speakers 8 ohm, 2W, with connector to our Power Supply Unit PCB <gallery> File:Speakers1.png </gallery> d0978c946765ff7f59437337e5a68724a92ff64b 829 828 2022-09-28T12:50:37Z Admin 1 /* Balthazar Instruction Manual */ wikitext text/x-wiki == Balthazar Instruction Manual == In the video below, it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable Type A or a combined, while the flat 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB or a flat cable. The touchpad and small screen are connected to a I2C that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis (in development). Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} Internal connections are also available for camera adoptions, as it is shown on the video below. {{#evt: service=youtube |id=https://youtu.be/Nm6NnHadsa0 |alignment=center }} '''GPIO''' cable we implement is ribbon cable with IDC connectors; 40x28AWG; Cable ph: 1.27mm. <gallery> File:Gpio cable.png </gallery> Speakers 8 ohm, 2W, with connector to our Power Supply Unit PCB <gallery> File:Speakers1.png </gallery> 63890e0aff3e3eeef443c5bc7c804587a1ea151a 831 829 2022-09-30T19:37:35Z Admin 1 wikitext text/x-wiki == Balthazar Instruction Manual == In the video below, it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable Type A or a combined, while the flat 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB or a flat cable. The touchpad and small screen are connected to a I2C that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis (in development). Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} Internal connections are also available for camera adoptions, as it is shown on the video below. {{#evt: service=youtube |id=https://youtu.be/Nm6NnHadsa0 |alignment=center }} '''GPIO''' cable we implement is ribbon cable with IDC connectors; 40x28AWG; Cable ph: 1.27mm. <gallery> File:Gpio cable.png </gallery> Speakers 8 ohm, 2W, with connector to our Power Supply Unit PCB <gallery> File:Speakers1.png </gallery> Space for batteries is reserved under the keyboard. At the moment Power Supply has been tested with Samsung battery with 4800 mAh and more specs are on our [[Specifications]] page. <gallery> File:Batt.5V out.png </gallery> 272c238d8aa4b67c6e6df56ad0fe269a0d24904a 6 172 814 2022-09-22T10:04:35Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 173 816 2022-09-22T10:09:50Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 174 818 2022-09-22T11:56:22Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 175 821 2022-09-22T12:04:43Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 176 823 2022-09-28T08:30:28Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 177 824 2022-09-28T08:32:45Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 129 826 806 2022-09-28T10:19:44Z Admin 1 /* Production process */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. Of course there will be issues with PCBs, also with obtaining elements for small orders and series, but updated designs are due and are updated on our [https://github.com/balthazar-space GitHub pages]. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarKeyboard3/issues here]. ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Video of assembling the Balthazar Unifying Board. {{#evt: service=youtube |id=https://youtu.be/ygKlJUs1uTE |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/Unifying-PCB/issues here]. ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarPSU3/issues here]. 6a43aedd5ea65b83e88c55500f9df3f859c8cc7f 832 826 2022-09-30T19:40:54Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. Of course there will be issues with PCBs, also with obtaining elements for small orders and series, but updated designs are due and are updated on our [https://github.com/balthazar-space GitHub pages]. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarKeyboard3/issues here]. ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Video of assembling the Balthazar Unifying Board. {{#evt: service=youtube |id=https://youtu.be/ygKlJUs1uTE |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/Unifying-PCB/issues here]. ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarPSU3/issues here]. ==== Battery ==== Battery is Samsung of 4800 mAh Where we test it with our Power Supply Unit A bit more info on a current battery choice is on our [[Specifications]] page. bf9ca0ee76c9eff5c0b1a18ac7a1ed80e61a1d35 833 832 2022-09-30T19:43:29Z Admin 1 /* Battery */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. Of course there will be issues with PCBs, also with obtaining elements for small orders and series, but updated designs are due and are updated on our [https://github.com/balthazar-space GitHub pages]. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarKeyboard3/issues here]. ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Video of assembling the Balthazar Unifying Board. {{#evt: service=youtube |id=https://youtu.be/ygKlJUs1uTE |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/Unifying-PCB/issues here]. ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarPSU3/issues here]. ==== Battery ==== Battery is Samsung of 4800 mAh. Here we test it with our Power Supply Unit A bit more info on a current battery choice is on our [[Specifications]] page. <gallery> File:Batt ch test12V.png|battery test </gallery> 92fccc3f3bf937c0603f92be611f0c6c01580dd9 834 833 2022-09-30T19:43:56Z Admin 1 /* Battery */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. Of course there will be issues with PCBs, also with obtaining elements for small orders and series, but updated designs are due and are updated on our [https://github.com/balthazar-space GitHub pages]. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarKeyboard3/issues here]. ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Video of assembling the Balthazar Unifying Board. {{#evt: service=youtube |id=https://youtu.be/ygKlJUs1uTE |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/Unifying-PCB/issues here]. ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarPSU3/issues here]. ==== Battery ==== Battery is Samsung of 4800 mAh. Here we test it with our Power Supply Unit. A bit more info on a current battery choice is on our [[Specifications]] page. <gallery> File:Batt ch test12V.png|battery test </gallery> 01f59b6ff9f81879d9929d0c6a9272a20b3ab9dd 837 834 2022-10-01T09:12:11Z Admin 1 /* Battery */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. Of course there will be issues with PCBs, also with obtaining elements for small orders and series, but updated designs are due and are updated on our [https://github.com/balthazar-space GitHub pages]. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarKeyboard3/issues here]. ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Video of assembling the Balthazar Unifying Board. {{#evt: service=youtube |id=https://youtu.be/ygKlJUs1uTE |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/Unifying-PCB/issues here]. ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarPSU3/issues here]. ==== Battery ==== Battery currently tested is Samsung 4800 mAh. Here we test it with our Power Supply Unit. A bit more info on a current battery choice is on our [[Specifications]] page. <gallery> File:Batt ch test12V.png|battery test </gallery> ddfb04cf5892d20fc9d892a99a54d77b3c303ea7 854 837 2022-10-28T20:35:33Z Admin 1 wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. Of course there will be issues with PCBs, also with obtaining elements for small orders and series, but updated designs are due and are updated on our [https://github.com/balthazar-space GitHub pages]. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarKeyboard3/issues here]. ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Video of assembling the Balthazar Unifying Board. {{#evt: service=youtube |id=https://youtu.be/ygKlJUs1uTE |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/Unifying-PCB/issues here]. ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarPSU3/issues here]. ==== Battery ==== Battery currently tested is Samsung 4800 mAh. Here we test it with our Power Supply Unit. A bit more info on a current battery choice is on our [[Specifications]] page. <gallery> File:Batt ch test12V.png|battery test </gallery> ==== Case ==== <gallery> File:10.png File:11.png File:12.png File:13.png File:15.png File:16.png File:17.png File:18.png </gallery> 030cc25a4c505a411f7e8adeb98e5cbae044d575 6 178 827 2022-09-28T11:00:27Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 46 830 785 2022-09-29T07:24:43Z Admin 1 /* September 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. ca9c5d2a0ca15e75c59bc9e2b810b5c1a0fee348 840 830 2022-10-01T09:29:16Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, reversioned and assembled PCBs with no or lot less issues that we can put in tests and present it as a working prototype, hopefully at the end of this month. ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. deaa2f81235a0eb29f5a7840e0f720fe2743e1b5 841 840 2022-10-03T08:26:57Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. bbe857123b8f1278865360b7e733cfaafa73648f 843 841 2022-10-06T12:37:51Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. d8360c31c77e2bbb6c8fc89a6a9ff7cc6f440e9c 845 843 2022-10-11T11:47:18Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 94af84847fe1bf79d447ecf5e6475cb235114871 859 845 2022-10-28T20:40:02Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 6b5387991efe36fd6afdde974078b37e373d4d2e 0 1 835 684 2022-10-01T09:02:16Z Admin 1 wikitext text/x-wiki __NOTOC__ == <center><strong>a Personal Computing Device</strong></center> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:P3.resized.png|center|prototype]] <gallery mode=packed> File:P1.resized.png|thumb| File:P2.resized.png|thumb| File:P4.resized.png|thumb| </gallery> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture or FPGA boards running emulation as a Computing Module Standard boards and other Systems on a Module that run on '''[https://www.linux.org Linux OS]''' or all of those running together with added co-processing power such as FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. Its default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Documentation]] and [[Instruction Manual]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> 41e1344bba7afe8ce479358d411d051cfb3e36c4 836 835 2022-10-01T09:05:26Z Admin 1 /* a Personal Computing Device */ wikitext text/x-wiki __NOTOC__ == <center><strong>a Personal Computing Device</strong></center> == <center><strong><big>One laptop for the new internet.</big></strong></center> <center>Secure, fast, inexpensive, open, robust, upgradeable, and sustainable. All of that.</center> [[File:P3.resized.png|center|prototype]] <gallery mode=packed> File:P1.resized.png|thumb| File:P2.resized.png|thumb| File:P4.resized.png|thumb| </gallery> '''BPCD''' - '''B'''althazar '''P'''ersonal '''C'''omputing '''D'''evice is a '''13.3"''' upgradable and expandable laptop that is based on a few concepts inspired by '''[https://www.crowdsupply.com/eoma68/micro-desktop/updates/2-7-5-cards-under-way-nlnet-and-intel-compute-card EOMA68]''', but powered by [https://riscv.org/ RISC-V] processor(s) open architecture or FPGA boards running emulation as a Computing Module Standard boards and other Systems on a Module that run on '''[https://www.linux.org Linux OS]''' or all of those running together with added co-processing power such as FPGA Lattice Diamond - [https://radiona.org/ulx3s/ ULX3S]. It contains all the hardware and continuously developing software and firmware features preventing data-theft and any unwanted 3<small>rd</small> party intrusion into the system by default. It should run default low-level security layer software based on [https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md '''LUKS''' ], [https://libreswan.org/ '''Libreswan'''] and is also envisaged to be '''[http://GNUnet.org/en/about.html GNUnet]''' ready. Its keyboard should be also inter-swappable with known x2xx ThinkPad keyboard replacement via developed adapter and a frame. While being versatile and robust it also follows '''CERN OSHL''', '''GNU-GPL''', '''FOSS''', '''ISA''' and even '''CC''' guidelines. <small>What is all that FOSS and CC and OS…?</small> '''→''' [[Glossary]]<br> <center><strong><big>'''For all children age 9-99.'''</big></strong></center> Want to know more?<br> <div style="background: #819ba3; margin: auto; column-count: 3;" class="menue"> * [[Goals]], [[Features]] and [[Specifications]] * [[News]] * [[FAQ|Frequently asked questions]] * [[Documentation]] and [[Instruction Manual]] * [[Links]] and [[Glossary]] * [[Contact|Contacts]] * [https://github.com/balthazar-space GitHub pages] </div> 1f0029880d6b621e489f1de6fb6e722c1ba395cb 6 179 842 2022-10-06T12:36:43Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 180 844 2022-10-11T11:45:58Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 181 846 2022-10-28T20:30:55Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 182 847 2022-10-28T20:31:37Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 183 848 2022-10-28T20:32:10Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 184 849 2022-10-28T20:32:43Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 185 850 2022-10-28T20:33:23Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 186 851 2022-10-28T20:33:53Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 187 852 2022-10-28T20:34:28Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 188 853 2022-10-28T20:35:13Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 189 855 2022-10-28T20:37:15Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 190 856 2022-10-28T20:37:46Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 191 857 2022-10-28T20:38:20Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 192 858 2022-10-28T20:39:03Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 193 860 2022-10-28T20:46:52Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 194 861 2022-10-28T20:48:00Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 46 862 859 2022-10-28T20:48:27Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. a2b689769791b4b9f1b5719eb5193e4de3434daa 880 862 2022-10-29T14:16:35Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. b0ca5dc9d63f9678ca1cc64f6b2cc8dd63af1738 881 880 2022-10-30T17:50:14Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> Here you can also see the 3D model of our upcomming prototype and have a preview. Some eleements are still developed, such as open-closing hinge system that we will try to implement, but overall idea is here. What for us is important to have proper dimensions and an internal set-up for modules. Please click [herehttps://skfb.ly/ozF6W here] and [https://skfb.ly/ozF7w here] and rotate and see for yourself. ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 08ba355b598e80c5ae558c7221ef37b6014bd4d5 882 881 2022-10-30T17:51:17Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> Here you can also see the 3D model of our upcomming prototype and have a preview. Some eleements are still developed, such as open-closing hinge system that we will try to implement, but overall idea is here. What for us is important to have proper dimensions and an internal set-up for modules. Please click [https://skfb.ly/ozF6W here] and [https://skfb.ly/ozF7w here] and rotate and see for yourself. ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 5534397f47b6d5f56995f35d649a1e35a2e00b52 883 882 2022-10-30T17:53:07Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> Here you can also see the 3D model of our upcomming prototype and have a preview. Some eleements are still developed, such as open-closing hinge system that we will try to implement, but the overall idea is here. What for us is very important is to have proper dimensions and an internal set-up for modules with proper dimensions. Please click [https://skfb.ly/ozF6W here] and [https://skfb.ly/ozF7w here] and rotate and see for yourself. ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. d43a95b8fed1b95d6a011f07f787639752392a88 884 883 2022-10-30T17:55:37Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> Here you can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall idea is here. What for us is very important is to have proper dimensions and an internal set-up for modules with proper dimensions. Please click [https://skfb.ly/ozF6W here] and [https://skfb.ly/ozF7w here] and rotate and see for yourself. ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 72017a993ec8e3abe69d4001b6c879c13d4d153d 885 884 2022-10-30T17:56:47Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> Here you can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall idea is here. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. Please click [https://skfb.ly/ozF6W here] and [https://skfb.ly/ozF7w here] and rotate and see for yourself. ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 4d45fa63c5ca8905a03a2cc907f4a5eabe38852f 886 885 2022-10-31T07:03:10Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. Status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> Here you can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall idea is here. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up version is in print already, and early next month we will post a video of all the modules working in the housing with a screen. Please click [https://skfb.ly/ozF6W here] and [https://skfb.ly/ozF7w here] and rotate and see for yourself. ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. c6f2168aaffcf07811545a951ee1e4b2f9440ca2 893 886 2022-10-31T15:32:25Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. ce90fdd9385c8aeaf1d21ca4434dabfe25650098 894 893 2022-10-31T15:44:50Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be improved as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 635dd3de7beacc0fd2ed1557f5001b1f2afd695b 895 894 2022-10-31T16:30:21Z Admin 1 /* October 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 0109d2bf9f40f1a0030ddda71ba1a0634a5d9a58 896 895 2022-11-01T10:39:45Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test design and an aestetic appeal ironed out. ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. b8c399ba588a523cb50c23b74cd21eed925ac013 897 896 2022-11-01T10:41:38Z Admin 1 /* November 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. eb663b8267b85533ac63ee695f59a737fc6fe3f5 899 897 2022-11-08T08:52:04Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled and those are being tested. More to come real soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 9504a9683ed7ca43ac62ff79fee03e742cb7881f 901 899 2022-11-08T09:06:32Z Admin 1 /* November 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. fbacd6fee90f3406ba3712a0e2351e88b7c05eb9 904 901 2022-11-22T09:05:51Z Admin 1 /* November 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 634b6b835aac9c9965073fe8dc7a15562aed8aa2 906 904 2022-11-22T09:10:29Z Admin 1 /* November 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 35a7a85d18d329f754b49d731aabfc1f31f28d60 910 906 2022-12-05T20:06:35Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==November 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer and we wait to hear from our partners on solutions for closing - openning systems. Alsp fpr us, the ergonomic aspect of the case as in the whole leaptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. f36dae71367c2f985780e4521126cb68ae31b5e6 0 129 863 854 2022-10-28T21:05:49Z Admin 1 /* Case */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. Of course there will be issues with PCBs, also with obtaining elements for small orders and series, but updated designs are due and are updated on our [https://github.com/balthazar-space GitHub pages]. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarKeyboard3/issues here]. ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Video of assembling the Balthazar Unifying Board. {{#evt: service=youtube |id=https://youtu.be/ygKlJUs1uTE |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/Unifying-PCB/issues here]. ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarPSU3/issues here]. ==== Battery ==== Battery currently tested is Samsung 4800 mAh. Here we test it with our Power Supply Unit. A bit more info on a current battery choice is on our [[Specifications]] page. <gallery> File:Batt ch test12V.png|battery test </gallery> ==== Case ==== A proper dimensions and a set up with battery and modules incorporated into the casing. <gallery> File:10.png File:11.png File:12.png File:13.png File:15.png File:16.png File:17.png File:18.png </gallery> 523463353102fa5b81830b2dfdce4047b1f59ebb 868 863 2022-10-29T10:45:22Z Admin 1 /* Battery */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. Of course there will be issues with PCBs, also with obtaining elements for small orders and series, but updated designs are due and are updated on our [https://github.com/balthazar-space GitHub pages]. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarKeyboard3/issues here]. ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Video of assembling the Balthazar Unifying Board. {{#evt: service=youtube |id=https://youtu.be/ygKlJUs1uTE |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/Unifying-PCB/issues here]. ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarPSU3/issues here]. ==== Battery ==== Battery currently tested is Samsung 4800 mAh. Here we test it with our Power Supply Unit. A bit more info on a current battery choice is on our [[Specifications]] page. <gallery> File:Batt ch test12V.png|battery test </gallery> Here we have 4 a bit stronger and more durable battery pack that we will test for a future usage. In a prototype version we will try to use both of the packs and those are yet to be tested with our Power Supply Unit. <gallery> File:Bat1.png </gallery> ==== Case ==== A proper dimensions and a set up with battery and modules incorporated into the casing. <gallery> File:10.png File:11.png File:12.png File:13.png File:15.png File:16.png File:17.png File:18.png </gallery> cb9c93a8f22cf2019b9d2236d209ee0c90cf7ec3 909 868 2022-11-22T09:17:59Z Admin 1 /* Case */ wikitext text/x-wiki == Balthazar Modules set == Those are Balthazar's modules and adjoining devices top view. Below is a description of each module. All PCB modules are to be connected through with the flat and short USB cables of Type-A to a power supply PCB that also charges the batteries and controls the voltage. As it is shown in a video on our [[Instruction Manual|Instruction manual]] page. Power supply would need an external USB-C charger or a 12V wall charger. [[File:Bset2.png|center|Balthazar modules set]] ==Description of the Balthazar modules== '''1. Module''' [[Power_Supply|Balthazar PSU]] is a combined battery charger, buck-boost converter and stereo power amplifier. It also delivers the power to the whole modular system, also via flat USB cable. '''Technical description:''' Universal power adapter – 12Vdc/5A (60VA Max) – the most usual laptop power connector / either exterior or inserted into chassis skeleton Input RFI filter Buck/ boost converter - 5-15V -> 5.1V (which is VSYS voltage on mainboard) LiPo battery pack single-cell charger -> from SYS voltage 5.1V Up to a large LiPo battery pack (10000mAh) – single cells / in parallel = 3.6V – three-terminal connector (-Vbat=gnd, thermistor NTC_TS, +Vbat=3.6V) Options: charge to/from/use external 5V battery pack (USB-A and/or USB-C connectors), solar panel charger. VSYS voltage is the main motherboard voltage line – use appropriate buck or boost converters on all separate functional modules (CPU, graphics, ram, etc.) [[File:PSU.png|center|PSU]] '''2. Module''' [[Keyboard|Balthazar Keyboard]] is a simplified, a bit ergonomic computer keyboard with DIY approach. In the two versions. The second iteration of the updated keyboard is to have some more geometric consistency. '''Description:''' The computer keyboard system with microcontroller (for now an 8-bit Atmel built into a small Sparkfun ProMicro board) A normal ISO keyboard layout is used. An option is given to test the ability of the microcontroller to handle also the control for the PSU board and the touchpad module data transfer to USB. Keypad and touchpad user activities are usually mutually exclusive – so this seems ok. Charger control is active a couple of seconds on startup of the system, so this is also ok. In case of some charger error, there is a mechanical switch on the PSU board to stop charging. In this way, three functions would be fulfilled in a single microcontroller – connected to the system with one USB. On the keyboard, there is also I2C to which the small screen and touchpad are connected to. [[File:Keyboard.png|center|Keyboard]] '''3. Module''' [[I/O USB|Balthazar IO]] is a simple USB2.0 four-port hub for the internal devices: keyboard and touchpad (optional trackpad), webcam and optional audio card. This is for an internal connection only and if the user wants to use a variant of some other ARM based systems, such as Raspberry Pi 4, or something compatible. End user will also have to disconnect and take out Unifying board, as that place is envisaged for such additional system. '''Description:''' The GL850G (ssop28-pin) four-port USB 2.0 hub chip with additional two pieces of AIC1526-0 dual USB high-side switch – to switch-off/on manually. It is a well-proven design. Hub will be powered via the upstream port – connected to the mini-computer board. Internal USB periphery power demands are predictable = low, so the usual 500mA limit for the hub is ok. The keyboard + touchpad combination is USB1.1 protocol, web cam, and optional audio card are USB2.0. [[File:IO.png|center|Input-Output]] '''4. Module''' [[Unifying-PCB|Unifying PCB]] is a single PCB solution for connecting the three previously designed Balthazar modules I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. '''Description:''' Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. Aimed at setting a compatibility standard to widely accepted hardware standards. It has standardized 100 pin accomodating module for adding standard CM HAT modules based on ARM or FPGA It has GPIO expansion port, HDMI,2x USB 3.0, Ethernet RJ45 and a microSD card slot. [[File:Unifying1.png|center|Unifying Board]] === Production process === This is the production process of each module as those progresses. iBoM for each module is in the respective folder on our [https://github.com/balthazar-space Github page]. Production start and a process with a PCB module of the keyboard, Power Supply Unit I/O and Unifying Board is shown below. For the [https://github.com/balthazar-space/balthazarKeyboard3 keyboard module], an interactive [https://github.com/openscopeproject/InteractiveHtmlBom iBoM (interactive Bill of materials)] is created, so one can use it in KiCad program for an easy overview and assembly. [https://github.com/balthazar-space/balthazarKeyboard3/blob/main/kitspace.yaml Balthazar Keyboard], [https://github.com/balthazar-space/balthazarPSU3/blob/main/kitspace.yaml PSU I/O] and [https://github.com/balthazar-space/Unifying-PCB/blob/main/kitspace.yaml Unifying PCB] can be found on our [https://github.com/balthazar-space Github page.] We used [https://kitspace.org/ Kitspace] to align the iBoM and see all the elements that we need for the production of our modules. Of course there will be issues with PCBs, also with obtaining elements for small orders and series, but updated designs are due and are updated on our [https://github.com/balthazar-space GitHub pages]. ==== Balthazar Keyboard ==== Keyboard production images, to encourage and visualise building process. <gallery> File:KeyBoard3 sourced.png|thumb| File:Kitspace.png|thumb| File:Balt keyboard.png|thumb| File:Keyboard prod.png|thumb| File:Keyboard full bottom.png|thumb| </gallery> Video of Balthazar Keyboard production. Shown elements are traced and soldered. {{#evt: service=youtube |id=https://youtu.be/GkYKUhgLRGw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarKeyboard3/issues here]. ==== Unifying board ==== <gallery> File:Unify-sourced.png|thumb| File:Uni bott prod3.png|thumb| File:Uni-ass1.png|thumb| File:Unifying ass1.png|thumb| </gallery> Video of assembling the Balthazar Unifying Board. {{#evt: service=youtube |id=https://youtu.be/ygKlJUs1uTE |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/Unifying-PCB/issues here]. ==== PSU I/O board ==== Images of PSU board and a process of building those. <gallery> File:PSU3 sourced.png|thumb| File:Psu top1.png|thumb| File:Psu bott.png|thumb| </gallery> Video of building process of PSU I/O board. Elements highlighting and soldering. {{#evt: service=youtube |id=https://youtu.be/WVtRI4U6vOw |alignment=center }} Issues can be found on our Github page -> [https://github.com/balthazar-space/balthazarPSU3/issues here]. ==== Battery ==== Battery currently tested is Samsung 4800 mAh. Here we test it with our Power Supply Unit. A bit more info on a current battery choice is on our [[Specifications]] page. <gallery> File:Batt ch test12V.png|battery test </gallery> Here we have 4 a bit stronger and more durable battery pack that we will test for a future usage. In a prototype version we will try to use both of the packs and those are yet to be tested with our Power Supply Unit. <gallery> File:Bat1.png </gallery> ==== Case ==== A proper dimensions and a set up with battery and modules incorporated into the casing. Test printing the case elements and internal settings. A seam printing mode is tested. <gallery> File:10.png File:11.png File:12.png File:13.png File:15.png File:16.png File:17.png File:18.png File:Caseprint test.png File:Internal settings seam.png </gallery> e2883bf8472393fc932e16718f94fdbda79aa5f6 6 195 864 2022-10-29T10:38:47Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 196 865 2022-10-29T10:39:25Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 55 866 839 2022-10-29T10:40:11Z Admin 1 /* Battery */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Test screen on '''Unifying Board''' with CM4 module working. Also works in a full configuration. <gallery> File:DSI1 balt.screen.png File:MIPI display.png File:DSI1 balt cabling.png File:DSI1 balt fix.png </gallery> ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== For specific Balthazar keyboard, see: [[Keyboard]] We develop add-on PCB to accommodate well known and basically industry standard keyboard as it is found in ThinkPad x2XX series. This will enable users to use an inexpensive replacement keyboard should they have need for it. Casing design envisage accommodating frame to fix additional keyboard in place. Touchpad on specific Balthazar's keyboard is connected via I2C bus. ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Up to 6 batteries are proposed to power Balthazar, however an additional Baterry Control Monitor should be implemented or as separate unit. Also research into other battery systems is done. Current battery candidate implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> Those are battery packs we assembled and into the carrier that fits into the case. In our prototype phase, we implemented those without Battery Charger Monitor. Next stage will be with a BCM PCB. <gallery> File:Bat2.png File:Bat3.png </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] 2a43ca883015820f5ae2bba852e0ea61903949a1 877 866 2022-10-29T14:12:41Z Admin 1 /* Battery */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Test screen on '''Unifying Board''' with CM4 module working. Also works in a full configuration. <gallery> File:DSI1 balt.screen.png File:MIPI display.png File:DSI1 balt cabling.png File:DSI1 balt fix.png </gallery> ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also the idea of a modular design gave us even more sustainable materials to look at - pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and a certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and a phases of the development: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== For specific Balthazar keyboard, see: [[Keyboard]] We develop add-on PCB to accommodate well known and basically industry standard keyboard as it is found in ThinkPad x2XX series. This will enable users to use an inexpensive replacement keyboard should they have need for it. Casing design envisage accommodating frame to fix additional keyboard in place. Touchpad on specific Balthazar's keyboard is connected via I2C bus. ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Up to 6 batteries are proposed to power Balthazar, however an additional Battery Control Monitor should be implemented or as a separate unit. Also, research into other battery systems is done. Current battery candidate implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> Those are battery packs we assembled and into the carrier that fits into the case. In our prototype phase, we implemented those without Battery Charger Monitor. Next stage will be with a BCM PCB. <gallery> File:Bat2.png File:Bat3.png </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] 61f959e6d98425ae410bb5c437ee1e5a54ccd42a 6 197 867 2022-10-29T10:44:21Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 198 869 2022-10-29T10:53:17Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 199 870 2022-10-29T10:54:44Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 200 871 2022-10-29T11:11:48Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 201 872 2022-10-29T11:14:19Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 108 873 535 2022-10-29T11:15:16Z Admin 1 /* Testing and probing */ wikitext text/x-wiki === Screen panel specs and features === Those are screen specifications that we took as a minimum requirements Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm === Testing and probing === Here are the photos of a screen testing running in a full resolution via our power supply, keyboard controller and with the help of a clone SoM R4, running Raspbian. Also raw screen not connected for a reference. <gallery> File:Sc1.png File:Sc2.png File:ScreenPS1.png File:ScreenSoM.png File:ScreenTest1.png File:ScreenTest2.png </gallery> Here are the other screens we used to test this configuration. <gallery> File:LCD 2.png File:LCD 1.png </gallery> 35e131e35a49146c93219e6e762327494a0098b7 874 873 2022-10-29T12:05:38Z Admin 1 /* Testing and probing */ wikitext text/x-wiki === Screen panel specs and features === Those are screen specifications that we took as a minimum requirements Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm === Testing and probing === Here are the photos of a screen testing running in a full resolution via our power supply, keyboard controller and with the help of a clone SoM R4, running Raspbian. Also raw screen not connected for a reference. <gallery> File:Sc1.png File:Sc2.png File:ScreenPS1.png File:ScreenSoM.png File:ScreenTest1.png File:ScreenTest2.png </gallery> Here are the other screens we used to test this configuration. Also we are looking into option of connecting smaller screens. There was also a design idea to have two smaller screens next to each other. <gallery> File:LCD 2.png File:LCD 1.png </gallery> 016bd300ed2523df3941e040a5b4c12fde7457f5 875 874 2022-10-29T14:07:47Z Admin 1 /* Testing and probing */ wikitext text/x-wiki === Screen panel specs and features === Those are screen specifications that we took as a minimum requirements Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm === Testing and probing === Here are the photos of a screen testing running in a full resolution via our power supply, keyboard controller and with the help of a clone SoM R4, running Raspbian. Also raw screen not connected for a reference. 13'3 inch screen as tested requires external driver. <gallery> File:Sc1.png File:Sc2.png File:ScreenPS1.png File:ScreenSoM.png File:ScreenTest1.png File:ScreenTest2.png </gallery> Here are the other screens we used to test this configuration. Also, we are looking into the option of connecting a variety of smaller screens. There was also a design idea to have two smaller screens next to each other. <gallery> File:LCD 2.png File:LCD 1.png </gallery> 76c356101865e201a0283bb9e0e4fde62a3d048a 876 875 2022-10-29T14:08:59Z Admin 1 /* Testing and probing */ wikitext text/x-wiki === Screen panel specs and features === Those are screen specifications that we took as a minimum requirements Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support color: 16.7M Color Depth: 8 bit Color Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm === Testing and probing === Here are the photos of a screen testing running in a full resolution via our power supply, keyboard controller and with the help of a clone SoM R4, running Raspbian. Also raw screen not connected for a reference. 13'3 inch screen as tested requires external driver. <gallery> File:Sc1.png File:Sc2.png File:ScreenPS1.png File:ScreenSoM.png File:ScreenTest1.png File:ScreenTest2.png </gallery> Here are the other screens we used to test this configuration. Also, we are looking into the option of connecting a variety of smaller screens. Those can be connected directly and do not require external driver PCB. There was also a design idea to have two smaller screens next to each other. <gallery> File:LCD 2.png File:LCD 1.png </gallery> 540cfe6d07c91216bcf9d936d0adb22b7ce5bb75 6 202 878 2022-10-29T14:14:55Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 203 879 2022-10-29T14:16:18Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 143 887 831 2022-10-31T09:53:59Z Admin 1 /* Balthazar Instruction Manual */ wikitext text/x-wiki == Balthazar Instruction Manual == In the video below, it is illustrated how Balthazar modules and components are connected and how it all fits into the case. '''Description:''' Main modules – [[Power Supply|PSU]], [[I/O USB|I/O board]], [[Keyboard|the keyboard]] and [[Unifying-PCB|Unifying board]] are connected via a flat and short USB cable Type A or a combined, while the flat 2-wire cable connects to a speaker. 3-wire flat cables are used to connect to the battery pack. Camera goes into the unifying board via USB or a flat cable. The touchpad and small screen are connected to a I2C that is on the keyboard PCB. The screen is connected to a Unifying Board that also has a video output. All the elements are placed into the casing and screwed to a chassis (in development). Upper covers of the keyboard are fitted. {{#evt: service=youtube |id=https://youtu.be/GN7CpjQyBcs |alignment=center }} Internal connections are also available for camera adoptions, as it is shown on the video below. {{#evt: service=youtube |id=https://youtu.be/Nm6NnHadsa0 |alignment=center }} '''GPIO''' cable we implement is ribbon cable with IDC connectors; 40x28AWG; Cable ph: 1.27mm. <gallery> File:Gpio cable.png </gallery> Speakers 8 ohm, 2W, with connector to our Power Supply Unit PCB <gallery> File:Speakers1.png </gallery> Space for batteries is reserved under the keyboard. At the moment Power Supply has been tested with Samsung battery with 4800 mAh and more specs are on our [[Specifications]] page. <gallery> File:Batt.5V out.png File:8.png </gallery> f9ed3fe6f361ba7d8a0663a872ac9c2dcc649cad 0 5 888 637 2022-10-31T10:56:21Z Admin 1 /* Current internals layouts */ wikitext text/x-wiki __NOTOC__ This page document features from a more user-centric point of view. For a more engineering point of view, see [[Specifications]]. ==Basic specifications and features</big>== '''Balthazar''' is made to run '''[https://nixos.org/ NixOS]''', '''[https://trisquel.info Trisquel GNU]''', '''[http://guix.gnu.org/ Guix]''', '''[https://www.debian.org Debian]''' and '''[https://www.ubuntu.com Ubuntu]''' variants of '''64 bit''' '''low-latency kernel''' for '''RISC-V'''.<br> In a form factor, there are some improvements and novelties in approach to a physical user interface and experience. The main characteristics of '''Balthazar''' are 4 robust hardware switches for WiFi, camera, microphones, and speakers, SoM CPU/GPU swappable card, a removable camera module with 2 microphones array, a keyboard layout with a segmented touch-pad positioned ''' above''' the keyboard with pull-out speakers. Motherboard(s) components are behind the screen and below the keyboard are batteries - one small non-removable and one big that is hot-swappable - SSD bay is also below the keyboard, as well as other peripheral connectors - GPIO, USB OTG-secure, HDMI, headphones, and mic inputs, volume knob and finally eSATA.<br> When the display lid is closed it engages the magnetic switch based on the "Timer Manager Module" and cuts off the power to all of the I/O modules preventing any remote "switch-on" possibility even before it suspends to RAM. The keyboard is '''QUERTY''' with 7 '''LED'''s illuminated and clickable 8 mm trackball positioned between G and H keys and above B key. It is based on '''Cherry MX''' low profile gaming switches<br> So when we say the "design is different", it actually is inspired by and extracted from '''[https://www.lenovo.com/gb/en/think/ IBM/Lenovo ThinkPad]''' series, '''[https://na.panasonic.com/us/computers-tablets-handhelds/computers/ Panasonic ToughBook]''',a '''[https://en.wikipedia.org/wiki/One_Laptop_per_Child OLPC]''' and main secure USB-dongle features based on '''[https://www.nitrokey.com/ Nitrokey]''' concept. Balthazar's design aims for a new usability experience.<br> ''"10 or so years ago there were no mobile phones, but we all learned how to use them."'' ([https://www.youtube.com/watch?v=8rJTJ_wA2NY Arjen Kamphuis in xTED speech in Delft)]<br> [[Image:BalthazarSet G1 2.png]] ===Current internals layouts=== Here we played with our developed boards' inner layout possibilities. While designing the housing and hinging we will update those designs and the inner concept regularly. <gallery> File:InnerLO.png|thumb| File:7.png </gallery> ===Components=== '''CPU and RAM''' - as the development goes on '''BPCD''' is based on '''RISC-V''' and '''ISA''' architecture multi-core '''SoM''' or a System on a Module "card" that is exchangeable and upgradeble. Added to it is FPGA co-processor based on a ingenious design by [https://radiona.org/ Radiona - a MakerSpace from Zagreb, Croatia] - [https://radiona.org/ulx3s/ ULX3S].<br> '''[https://riscv.org/ RISC-V]''' architecture is understood as an ideal vehicle for the security community.<br> We also keep an eye on '''ARM Cortex''' - '''A7x''' iterations along the path, waiting for their development to align with our expectations which are open documentation that will enable the Open Source community to write drivers and other software.<br> With a maximum reasonable amount of '''RAM''', we use the most rational clock speeds to achieve the best possible computing performance versus battery power consumption. There should be no compromise there. In any case, count on 8+ Gb RAM and some serious processing power. '''GPU''' - '''ARM''''s '''MALI-4xx''' architecture would do great, but we also look into drivers' compatibility and openness, too.<br> While '''NVIDIA''' would be technically possibly the best performance choice, issues arise with a general attitude towards '''FOSS''' compatibility.<br> In any case we look and listen into '''NVIDIA''' and '''CUDA''' options, accelerating totally open documentation from '''NVIDIA''''s side.<br> Also the '''NVIDIA's Jetson''' IoT and AI platform is researched for a compatibility with '''RISC-V''' architecture, '''ISA''' and '''FOSS''' .<br> '''Storage''' - a '''SATA''' SSD is on board and it should be taken out very fast from a bay.<br> '''eSATA''' connector might help in expanding the storage possibilities.<br> '''Fanless''' - less movable parts means more battery time for the processing power and a '''passive cooling''' adds to the longevity of the components. Think quiet.<br> '''Boot and sleep''' - Secure-boot as well as a fast boot time. Nobody has and especially children do not have the patience to wait.<br> Ever since '''C64/AMIGA''' times computers should be able to be switched on and off fast, so using some '''Libreboot/Coreboot''' and a '''Clear Linux''' (minus Intel optimisation) concepts applied in a '''BPCD''' firmware/BIOS should do it.<br> '''BPCD''' suspends to '''RAM''' and goes to hibernate when battery is at 20%. Properly.<br> '''Upgradeable''' - RAM and a processor-board featuring '''SoM''' attachment port.<br> '''A non-glare screen''' - size is 13.3” 16:10 full HD resolution (200 dpi +) that provides far less strain on user's eyes.<br> '''A non-reflective'' - a button drove backlight “off” monochrome mode for very low-power use in sunlight - prolongs a battery life a lot.<br> '''LED backlit''' - color mode with an alternate of red, green, and blue pixels.<br> '''A detachable webcam''' - also with a slide lens cover and a hardware switch for on/off<br> '''A volume wheel''' - a ceramic volume potentiometer with a “click” for the on/off functionality.<br> '''GPIO''' - a retractable and flexible robust flat-ribbon cable connecting General Purpose Input Output 19 pins array for connecting to all the things you want to connect it to.<br> '''Quick charging battery''' - Long Life Cycle Polymer 10000+ mAh that is also recyclable.<br> '''Hot-swap''' - a second small battery enabling main battery hot-swap.<br> '''Modular power''' - on-board power supply that follows full '''ACPI''' specification defaults to scalable/modular voltage for the processor and memory by the design aims at preventing the so-called ''side-channel'' attacks. '''ISA''' already specifies that no data is kept in the cache, but the remote possibility of such an attack still exists.<br> '''Waterproof keyboard''' - with an illuminated track-point ball, firmware includes default onboard SSH compression (ssh -C) enabled communication between keyboard's motherboard and the rest of I/O hardware - prevents key-logging and keystroke timing and guessing algorithms.<br> '''Multitouch pad''' - a smooth surface, flat-flush and positioned '''above''' the keyboard. It has a “Wacom”-style mode for the extended stylus or a finger draw.<br> It is multi-touch and gestures capable.<br> '''Casing''' - a tough, rugged form-factor done in a multi-color polycarbonate, or aluminum composite, and recyclable plastic with maybe added LEGO® studs here and there.<br> ==Hardware security and privacy features== '''Four (4) hardware '''off/on''' switches''' - webcam (detachable), speakers, the microphones array (detachable) and obligatory Wi-Fi.<br> '''Detachable USB gender-changer dongle''' - that should prevent anyone to plug in USB-anything unless it is attached and a password unlocked, also when it is taken out prevents anyone to stick USB-anything in. Basically - a bit secured USB onboard.<br> ==A few interesting extras== '''TEMPEST-shield internal cabling''' - shields from any external and internal electromagnetic radiation. Weaved and braided cable shielding above MIL-SPEC/DTL and GOST/IST standards.<br> '''A stylus''' - for a pad drawing, also provides enhanced entropy while generating PGP keys, easy graphic editing, poking someone, etc.<br> ==Additional adapter with an onboard:== '''LEGO® Power Functions''' - for powering and the control of actuators. '''.<br> '''RJ-12 LEGO®''' - “a shifted notch” connector for '''LEGO® MINDSTORMS®''' series of actuators and sensors,<br> '''a male D-Sub serial port''' (tty) and a VGA connector.<br> ==Charms== '''LEGO® keychain''' - for the USB dongle.<br> [[Designs|Want to know more? Pretty pictures ahead.]] Or see [[Schematics]], [[Keyboard]], [[I/O_USB]], [[Power Supply]] and [[Screen panel]] . 6324ce7caaa8df748fea4756d9ff0b3eb26e9cf4 6 204 889 2022-10-31T15:28:47Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 205 890 2022-10-31T15:29:51Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 206 891 2022-10-31T15:30:41Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 207 892 2022-10-31T15:31:24Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 208 898 2022-11-08T08:46:18Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 209 900 2022-11-08T09:05:53Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 210 902 2022-11-22T08:59:52Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 211 903 2022-11-22T09:04:16Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 212 905 2022-11-22T09:10:08Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 213 907 2022-11-22T09:15:00Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 214 908 2022-11-22T09:17:40Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 46 911 910 2022-12-05T20:07:02Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer and we wait to hear from our partners on solutions for closing - openning systems. Alsp fpr us, the ergonomic aspect of the case as in the whole leaptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 1b82a37d289af6a7af80d71f09b647e2c440c2fe 912 911 2023-01-03T08:25:07Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer and we wait to hear from our partners on solutions for closing - openning systems. Alsp fpr us, the ergonomic aspect of the case as in the whole leaptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 8f25fce445d3c52bbaf7c02420186811a7786869 913 912 2023-01-03T08:27:05Z Admin 1 /* December 2022 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 000b0404f2afdffbe072f533f417edbca79a5dd5 916 913 2023-03-20T09:32:50Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. aaf988711aff4650df15ce67414d35c2fa02782a 917 916 2023-04-03T14:02:26Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 76f5fe904d2594b619832f0af9144817474867e2 918 917 2023-05-08T11:37:00Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from THink Pad X2xx series. Also included to an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 330c062415da0a13ea6496852ed1719c3f809844 919 918 2023-05-08T11:37:39Z Admin 1 /* May 2023 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 9382c825703419a04dfdc30e18d2650d8136efe8 920 919 2023-06-05T10:50:30Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 53ac7c797006fd6837ab063d4f4007d35c51dc6d 929 920 2023-07-03T11:46:29Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August. Since we managed to engage a professional designer that has a long history in the business, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 1e4749e8a9c2855944e8101096a35e738aba25f1 6 216 915 2023-03-04T21:43:29Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 217 921 2023-07-03T11:30:40Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 218 922 2023-07-03T11:34:23Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 219 923 2023-07-03T11:35:55Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 220 924 2023-07-03T11:36:44Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 221 925 2023-07-03T11:37:54Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 222 926 2023-07-03T11:38:37Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 223 927 2023-07-03T11:39:12Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 224 928 2023-07-03T11:46:06Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 225 930 2023-07-26T13:18:03Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 226 931 2023-07-26T13:21:48Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 227 932 2023-07-26T13:24:07Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 228 933 2023-07-26T13:29:11Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 229 934 2023-07-26T13:30:38Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 230 935 2023-07-26T13:31:41Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 231 936 2023-07-26T13:34:02Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 232 937 2023-07-26T13:35:44Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 233 938 2023-07-26T14:15:11Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 234 939 2023-07-26T14:16:11Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 235 940 2023-07-26T14:18:54Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 236 941 2023-07-26T14:19:38Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 237 942 2023-07-26T14:21:10Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 238 943 2023-07-26T14:22:20Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 239 944 2023-07-26T14:23:03Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 240 945 2023-07-26T14:23:45Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 241 946 2023-07-26T14:24:25Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 242 947 2023-07-26T14:26:05Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 243 948 2023-07-26T14:26:43Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 244 949 2023-07-26T14:27:28Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 245 950 2023-07-26T14:28:27Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 246 951 2023-07-26T14:29:47Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 247 952 2023-07-26T14:30:26Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 248 953 2023-07-26T14:31:07Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 249 954 2023-07-26T14:31:49Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 250 955 2023-07-26T14:32:59Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 251 956 2023-07-26T14:33:41Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 252 957 2023-07-26T14:34:36Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 253 958 2023-07-26T14:35:49Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 254 959 2023-07-26T14:36:54Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 255 960 2023-07-26T14:37:48Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 55 961 877 2023-07-26T14:38:36Z Admin 1 /* Case */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Test screen on '''Unifying Board''' with CM4 module working. Also works in a full configuration. <gallery> File:DSI1 balt.screen.png File:MIPI display.png File:DSI1 balt cabling.png File:DSI1 balt fix.png </gallery> ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also, the idea of a modular design gave us even more sustainable materials to look at – pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and phases of the development, with the newest developments on the top. Below is shown a construction of a casing, with all the elements fitting in. This prototype is consisting of 4 cover units and 7 lower units inclusive the hinge. All construction elements are stitched using small orange plastic pegs. <gallery> File:Const2.r2.png File:Const3.r3.png File:Const4.r4.png File:Const5.r5.png File:Const6.r6.png File:Const19.r19.png File:Const18.r18.png File:Const10.r10.png File:Const17.r17.png File:Const24.r24.png File:Const25.r25.png File:Const26.r26.png File:Const32.r32.png File:Const19.r19.png File:Const22.r22.png File:Const21.r21.png File:Const23.r23.png File:Const27.r27.png File:Const28.r28.png File:Const33.r33.png File:Const34.r34.png File:Const7.r7.png File:Const9.r9.png File:Const10.r10.png File:Const12.r12.png File:Const15.r15.png File:Const14.r14.png File:Const11.r11.png File:Const16.r16.png File:Const30.r30.png File:Const31.r31.png File:Const hinge1.r35.png </gallery> This was a first trial of constructing the case and modular elements below: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== For specific Balthazar keyboard, see: [[Keyboard]] We develop add-on PCB to accommodate well known and basically industry standard keyboard as it is found in ThinkPad x2XX series. This will enable users to use an inexpensive replacement keyboard should they have need for it. Casing design envisage accommodating frame to fix additional keyboard in place. Touchpad on specific Balthazar's keyboard is connected via I2C bus. ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Up to 6 batteries are proposed to power Balthazar, however an additional Battery Control Monitor should be implemented or as a separate unit. Also, research into other battery systems is done. Current battery candidate implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> Those are battery packs we assembled and into the carrier that fits into the case. In our prototype phase, we implemented those without Battery Charger Monitor. Next stage will be with a BCM PCB. <gallery> File:Bat2.png File:Bat3.png </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] 2b469c927bd7d7012d42d584cb82d58e015f221d 0 55 962 961 2023-07-26T14:42:05Z Admin 1 /* Case */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Test screen on '''Unifying Board''' with CM4 module working. Also works in a full configuration. <gallery> File:DSI1 balt.screen.png File:MIPI display.png File:DSI1 balt cabling.png File:DSI1 balt fix.png </gallery> ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also, the idea of a modular design gave us even more sustainable materials to look at – pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the .stl files too. Chronological pictures and phases of the development, with the newest developments on the top. Below is shown a construction of a casing, with all the elements fitting in. This prototype is consisting of 4 cover units and 7 lower units inclusive the hinge. All construction elements are stitched using small orange plastic pegs. <gallery> File:Const2.r2.png File:Const3.r3.png File:Const4.r4.png File:Const5.r5.png File:Const6.r6.png File:Const18.r18.png File:Const10.r10.png File:Const17.r17.png File:Const24.r24.png File:Const25.r25.png File:Const26.r26.png File:Const32.r32.png File:Const19.r19.png File:Const22.r22.png File:Const21.r21.png File:Const23.r23.png File:Const27.r27.png File:Const28.r28.png File:Const33.r33.png File:Const34.r34.png File:Const7.r7.png File:Const9.r9.png File:Const10.r10.png File:Const12.r12.png File:Const15.r15.png File:Const14.r14.png File:Const11.r11.png File:Const16.r16.png File:Const30.r30.png File:Const31.r31.png File:Const hinge1.r35.png </gallery> This was a first trial of constructing the case and modular elements below: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== For specific Balthazar keyboard, see: [[Keyboard]] We develop add-on PCB to accommodate well known and basically industry standard keyboard as it is found in ThinkPad x2XX series. This will enable users to use an inexpensive replacement keyboard should they have need for it. Casing design envisage accommodating frame to fix additional keyboard in place. Touchpad on specific Balthazar's keyboard is connected via I2C bus. ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Up to 6 batteries are proposed to power Balthazar, however an additional Battery Control Monitor should be implemented or as a separate unit. Also, research into other battery systems is done. Current battery candidate implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> Those are battery packs we assembled and into the carrier that fits into the case. In our prototype phase, we implemented those without Battery Charger Monitor. Next stage will be with a BCM PCB. <gallery> File:Bat2.png File:Bat3.png </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] f5f0d25ef52a4b2b80e11b1c9f1a361c92746845 971 962 2023-08-24T10:15:36Z Admin 1 /* Case */ wikitext text/x-wiki __NOTOC__ This page documents features from more engineering point of view. For a more user-centric point of view, see [[Features]]. [[Image:BalthazarBlockDia122.svg]] Major Balthazar parts are: ==Power Controller and battery== These supply power to the rest of the system, particularly the System on a Module, USB Hub and Display subsytem. It also manages battery. It should be capable enough to run some USB connected hardware. See more: [[Power Supply]] ==System on a Module (SoM)== This is the main system board, ''the computer''. Boards from different makers should be supported. Minimum of ports is required for wider compaitibility. These are: Power, USB and HDMI. See more: [[System on a Module]] ==I/O USB hub== IO-board basically means connectivity with peripheral devices. These can be seen as on-board and out-board. On-board devices include: keyboard + trackpad, webcam and optional audio-card. USB is the usual solution for this. For more see our [[I/O USB]] page. ==Unifying-PCB== Single PCB solution for connecting the three previously designed Balthazar modules (I/O, power supply, USB 2.0, 3.0 controllers, keyboard and adding Compute Module compatible FPGA boards. For more info see our [[Unifying-PCB]] page. ==Display Controller and a [[screen panel]]== Provides interface to display panel by HDMI Panel slim screen. Resolution: 1920 x 1080 Aspect Ratio: 16:9 Pixel Pitch(mm): 0.1529 x 0.1529 PPI: 166 Active Area(mm): 294.06 x 165.54 Outline(mm): 299.96 x 186.92 Luminance(nits): 300 View Angle (U/D/R/L): 89/89/89/89 Contrast Ratio: 800:1 Support colour: 16.7M Colour Depth: 8 bit Colour Gamut (NTSC): 72% Response Time(ms): 25 Power consumption: 3.7 Backlight: LED Weight: 170 g Frame Rate: (Hz)60Hz Electrical Interface: DP 1.3 Ultra-slim thickness: 2mm Test screen on '''Unifying Board''' with CM4 module working. Also works in a full configuration. <gallery> File:DSI1 balt.screen.png File:MIPI display.png File:DSI1 balt cabling.png File:DSI1 balt fix.png </gallery> ==Case== Initial casing is meant to be made of a recyclable vegetable oil based plastic. Also, the idea of a modular design gave us even more sustainable materials to look at – pressed used clothes in resin, cans recycled pressed aluminium and even resin-ed wood saw. Here are elements we have been working with so far and slowly shaping the final design and certain materials together. On our [https://github.com/balthazar-space/case-and-design Github page] you can look into the print files too. Chronological pictures and phases of the development, with the newest developments on the top. Below is shown a latest construction of a casing, with all the elements fitting in. This prototype is consisting of 4 cover units and 7 lower units inclusive the hinge. All construction elements are stitched using small orange plastic pegs. <gallery> File:Const2.r2.png File:Const3.r3.png File:Const4.r4.png File:Const5.r5.png File:Const6.r6.png File:Const18.r18.png File:Const10.r10.png File:Const17.r17.png File:Const24.r24.png File:Const25.r25.png File:Const26.r26.png File:Const32.r32.png File:Const19.r19.png File:Const22.r22.png File:Const21.r21.png File:Const23.r23.png File:Const27.r27.png File:Const28.r28.png File:Const33.r33.png File:Const34.r34.png File:Const7.r7.png File:Const9.r9.png File:Const10.r10.png File:Const12.r12.png File:Const15.r15.png File:Const14.r14.png File:Const11.r11.png File:Const16.r16.png File:Const30.r30.png File:Const31.r31.png File:Const hinge1.r35.png </gallery> This was a first trial of constructing the case and modular elements below: <gallery> File:DownBody.png |thumb| File:Frame.png|thumb| File:KeyPad.png|thumb| File:ScreenBack.png|thumb| File:Speaker.png|thumb| File:Basic1.png|thumb| File:Basic2.png|thumb| File:Basic3.png|thumb| File:Basic4.png|thumb| File:Basic5.png|thumb| File:Basic6.png|thumb| File:Basic7.png|thumb| File:Basic8.png|thumb| File:P2.resized.png|thumb| </gallery> ==Keyboard and Touch-pad== For specific Balthazar keyboard, see: [[Keyboard]] We develop add-on PCB to accommodate well known and basically industry standard keyboard as it is found in ThinkPad x2XX series. This will enable users to use an inexpensive replacement keyboard should they have need for it. Casing design envisage accommodating frame to fix additional keyboard in place. Touchpad on specific Balthazar's keyboard is connected via I2C bus. ==Battery== We did implementation and tests with this battery set: Brand: Samsung Battery size: 21700 Battery chemistry: Li-ion Battery: Rechargeable Voltage 3.6V Min. capacity in mAh: 4,800.00 Battery version: Flat top Discharge current: 9.60 Protection circuit: Unprotected Height: 70.00 Diameter in mm: 21.00 Up to 6 batteries are proposed to power Balthazar, however an additional Battery Control Monitor should be implemented or as a separate unit. Also, research into other battery systems is done. Current battery candidate implementation and tests. Charging and operating. <gallery> File:Batt.5V out.png|5V File:Batt ch test12V.png|12V </gallery> Those are battery packs we assembled and into the carrier that fits into the case. In our prototype phase, we implemented those without Battery Charger Monitor. Next stage will be with a BCM PCB. <gallery> File:Bat2.png File:Bat3.png </gallery> ==OLED small screen for keyboard== OLED Module: display OLED 3.3÷5VDC I2C 33x20mm - 0.91" <gallery> File:Oled1.png </gallery> ==Software== Software depends on a System on a Module used. See more: [[Software]] ef6e8892dbbd2827da49542c3ed6e32b887cd566 0 46 963 929 2023-07-26T15:32:37Z Admin 1 /* July 2023 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August. Since we managed to engage a professional designer that has a long history in the business, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Case]] page with more pictures of construction self printed and stitched elements and modules: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 9615c4000d95f2c2c1ce27715279684fe4eb58c5 964 963 2023-07-26T15:34:15Z Admin 1 /* July 2023 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August. Since we managed to engage a professional designer that has a long history in the business, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction self printed and stitched elements and modules: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 5707ce9f3e3d9449a2deed8246e1423e11023570 965 964 2023-07-26T15:34:54Z Admin 1 /* July 2023 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August. Since we managed to engage a professional designer that has a long history in the business, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. c99fe56025105cd24d89e8b765e19d9355c25052 966 965 2023-08-06T20:28:48Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==August 2023== THis month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accomodating external replacement x2xx ThinkPad keyboards is being processed. More to come. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August. Since we managed to engage a professional designer that has a long history in the business, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 524f8b15725b11dd1299c3fc626d484167dd6d26 967 966 2023-08-18T12:53:25Z Admin 1 /* August 2023 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accomodating external replacement x2xx ThinkPad keyboards is being processed. More to come. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August. Since we managed to engage a professional designer that has a long history in the business, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. a4acdf1db345266044bc735a0d66c46203be5c33 968 967 2023-08-23T14:06:00Z Admin 1 /* August 2023 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accomodating external replacement x2xx ThinkPad keyboards is being processed. In September 26th to 27th 2023, we will attend the DIGITAL CITIZEN SOVEREIGNTY conference in Malaga, Spain at EmpoderaLIVE, where we will present our project and show what has been done so far. More info on that event is to be found [https://kt4democracy.eu/events/digital-citizen-sovereignty-under-construction here]. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August. Since we managed to engage a professional designer that has a long history in the business, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 7489f764698ad6123932efec4145f701cc5a5334 969 968 2023-08-23T14:11:35Z Admin 1 /* August 2023 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accomodating external replacement x2xx ThinkPad keyboards is being processed. In September 26th to 27th 2023, we will attend the DIGITAL CITIZEN SOVEREIGNTY conference in Malaga, Spain at EmpoderaLIVE, where we will present our project and show what has been done so far. More info on that event is to be found [https://empodera.org/live/en/ here]. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August. Since we managed to engage a professional designer that has a long history in the business, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 3a565d57ce51eca27c3f1ec9899dc0c2dd6c612f 970 969 2023-08-23T15:28:23Z Admin 1 /* July 2023 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accomodating external replacement x2xx ThinkPad keyboards is being processed. In September 26th to 27th 2023, we will attend the DIGITAL CITIZEN SOVEREIGNTY conference in Malaga, Spain at EmpoderaLIVE, where we will present our project and show what has been done so far. More info on that event is to be found [https://empodera.org/live/en/ here]. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. ccf50e58782e3271f0bd9bdf584bd046ba915e54 972 970 2023-08-25T11:16:18Z Admin 1 /* August 2023 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. ae8bdcd3ad84114c6133f0ee225186a4f4a0d80e 973 972 2023-09-06T08:01:02Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==September 2023== This month we will develop and present a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 6585e24f2e59d0fecc7f01088bb8dfa2469b0121 974 973 2023-10-04T08:37:37Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2023== We expect to have some viable designs upcoming dureing this month. The develoment of an additional click-on chip for adding external keyboard is in progress and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 00432ae2adfa69faab7d73f820724f2e5cb42d0a 975 974 2023-10-04T18:32:47Z Admin 1 /* October 2023 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 8b9244ea1c1640b61c4428eb6223c6be1f4659d2 976 975 2024-01-08T09:04:24Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interseting form factor and available. ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 60c1d923e04b2537033a26f808dd4a258985c2f9 978 976 2024-01-08T09:06:58Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interseting form factor and available. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. c1379fcb84223060d66d9dc06587711573c9c016 981 978 2024-02-04T12:15:55Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Mars, Orange. We have also scoured the web for the other's people expiriences. A set of cards and some comparisons are shown below. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interseting form factor and available. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 66649f903fb30f4f1f7f4a9583db77b1cb0fec79 983 981 2024-02-04T12:18:50Z Admin 1 /* January 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Mars, Orange. We have also scoured the web for the other's people expiriences. A set of cards and some comparisons are shown below. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interseting form factor and available. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. b7163eb47608695720709a10c81cb8542e9b5d57 984 983 2024-02-04T12:23:36Z Admin 1 /* January 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interseting form factor and available. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. a562823e4db1b2d99f7454cfa8ea1b1f3e2aa71a 985 984 2024-02-04T12:24:11Z Admin 1 /* December 2023 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 3e3b743a4c7a103495e3f0c9b5b0913e620b4881 986 985 2024-02-04T12:27:54Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also the frame to accomodate it in a fixed position. When ready pictures will be as per ususal, below. ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. a2eb9810c20040a433a5bac2d8484ce57d4f7cd0 987 986 2024-02-04T12:44:04Z Admin 1 /* January 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also the frame to accomodate it in a fixed position. When ready pictures will be as per ususal, below. ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 355c0280bc93da822adaa79c5a31da4ddcd3575a 988 987 2024-02-04T13:26:05Z Admin 1 /* February 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also the frame to accomodate it in a fixed position. When ready pictures will be as per usual, below. ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. a6fa926daad796be195838521eb1f670f67ab430 989 988 2024-02-04T13:26:27Z Admin 1 /* February 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. When ready pictures will be as per usual, below. ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. a03fd93985c2055ea67dbedac83221630e496b88 996 989 2024-02-13T12:51:12Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. When ready pictures will be as per usual, below. <gallery> File:1.png File:3.png File:4.png File:5.png File:6.png File:7.png File:8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. f9f77adad4e2f4f4c6e665fc364ed0e058d7354f 997 996 2024-02-13T13:36:46Z Admin 1 /* February 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. When ready pictures will be as per usual, below. <gallery> File:1.png File:3.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 6521df906320f31c609a4837d9ccb3c50021bfd5 998 997 2024-02-13T13:37:55Z Admin 1 /* February 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:1.png File:3.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 3a875117b98dbcb478bec0f91fd6bf9ad5860c39 1007 998 2024-02-13T21:27:31Z Admin 1 /* February 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 1d3a1aded42584a3a7fd28fad6a62d13cd0afbaf 1008 1007 2024-02-13T21:29:23Z Admin 1 /* February 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 340c70185e54bfaba09c48cb743653d90b13957b 1009 1008 2024-03-18T09:48:32Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==March 2024== So we havethe proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on thier design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 3a67df585d12ff46f4dd8418cdd1703b48125c66 1010 1009 2024-03-18T09:49:54Z Admin 1 /* March 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. f6ca3583a7434a616c9fb6835ddba72695fc0cb7 1011 1010 2024-06-04T15:13:16Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2024== There are couple of eInk options that we might order to test and see if there is a cost effective way to use 9 inch screen sizes. More as things fold in. ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. c2d0e9afac2dbce40f8ac6b88d78579cae60ffd8 6 256 977 2024-01-08T09:05:12Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 257 979 2024-02-04T12:13:17Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 258 980 2024-02-04T12:15:01Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 259 982 2024-02-04T12:18:32Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 260 990 2024-02-13T12:41:10Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 1005 990 2024-02-13T21:24:55Z Admin 1 Admin moved page [[File:1.png]] to [[File:Fr1.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 261 991 2024-02-13T12:43:04Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 1003 991 2024-02-13T21:24:24Z Admin 1 Admin moved page [[File:3.png]] to [[File:Fr3.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 189 992 855 2024-02-13T12:44:53Z Admin 1 Admin uploaded a new version of [[File:4.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 1001 992 2024-02-13T21:23:46Z Admin 1 Admin moved page [[File:4.png]] to [[File:Fr4.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 192 993 858 2024-02-13T12:46:27Z Admin 1 Admin uploaded a new version of [[File:8.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 995 993 2024-02-13T12:49:37Z Admin 1 Admin uploaded a new version of [[File:8.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 999 995 2024-02-13T21:18:46Z Admin 1 Admin moved page [[File:8.png]] to [[File:Fr8.png]] without leaving a redirect wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 190 994 856 2024-02-13T12:47:50Z Admin 1 Admin uploaded a new version of [[File:5.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 1000 994 2024-02-13T21:22:46Z Admin 1 Admin moved page [[File:5.png]] to [[File:Fr5.png]] without leaving a redirect wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 262 1002 2024-02-13T21:23:46Z Admin 1 Admin moved page [[File:4.png]] to [[File:Fr4.png]] wikitext text/x-wiki #REDIRECT [[File:Fr4.png]] 72b993129b0a2e0ca97a4c6f7d5eb4be14223bdf 6 263 1004 2024-02-13T21:24:24Z Admin 1 Admin moved page [[File:3.png]] to [[File:Fr3.png]] wikitext text/x-wiki #REDIRECT [[File:Fr3.png]] 240ff318c64682c6e3ac07119740ef45ef97b99b 6 264 1006 2024-02-13T21:24:55Z Admin 1 Admin moved page [[File:1.png]] to [[File:Fr1.png]] wikitext text/x-wiki #REDIRECT [[File:Fr1.png]] 5c6a88752cc70681aae9efa0581ba8cdfc7b11dd 6 265 1012 2024-06-04T15:17:12Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 46 1013 1011 2024-06-04T15:17:59Z Admin 1 /* May 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2024== There are couple of eInk options that we might order to test and see if there is a cost effective way to use 9 inch screen sizes. More as things fold in. ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. File:X230.jpg ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 0044cb1d49c8997efc9cea97fa3838e7f4e8f94f 1014 1013 2024-06-04T15:18:39Z Admin 1 /* May 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2024== There are couple of eInk options that we might order to test and see if there is a cost effective way to use 9 inch screen sizes. More as things fold in. ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. <gallery> File:X230.jpg </gallery> ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. a3644afc792091f8f35b762fb5d3613b3661e0a0 1015 1014 2024-06-18T09:53:23Z Admin 1 /* June 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2024== There are couple of eInk options that we might order to test and see if there is a cost effective way to use 9 inch screen sizes. More as things fold in. Also we will publish a new firmware for Balthazar keyboard during this month. ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. <gallery> File:X230.jpg </gallery> ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 9fe4dc53367a28b936eedb36fa4ebfe09eff509d 1016 1015 2024-06-18T10:50:57Z Admin 1 /* June 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2024== There are couple of eInk options that we might order to test and see if there is a cost effective way to use 9 inch screen sizes. More as things fold in. Also we will publish a new firmware for Balthazar keyboard during this month. It iwll be adopted to a small OLED screens situated on the keyboard namely using SH1106 128x64 or SSD1306 128x32. ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. <gallery> File:X230.jpg </gallery> ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. fbb5703822f6c2af7f3fcf79f94afe8c6ca658ce 1018 1016 2024-06-26T10:28:14Z Admin 1 /* June 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2024== There are couple of eInk options that we might order to test and see if there is a cost effective way to use 9 inch screen sizes. More as things fold in. Also we will publish a new firmware for Balthazar keyboard during this month. It iwll be adopted to a small OLED screens situated on the keyboard namely using SH1106 128x64 or SSD1306 128x32. Below is a working screen. <gallery> File:Oled.png </gallery> ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. <gallery> File:X230.jpg </gallery> ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 5d965c87c52d798f772b55e0c88ca4e504e0404c 1020 1018 2024-06-27T07:07:45Z Admin 1 /* June 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2024== There are couple of eInk options that we might order to test and see if there is a cost effective way to use 9 inch screen sizes. More as things fold in. Also we will publish a new firmware for Balthazar keyboard during this month. It iwll be adopted to a small OLED screens situated on the keyboard namely using SH1106 128x64 or SSD1306 128x32. Below is a working screen. <gallery> File:Oled.png File:Scr1.png </gallery> ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. <gallery> File:X230.jpg </gallery> ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 2f2390bcdc6bc715ea613dfd2927ba2d545a6ce9 1021 1020 2024-06-27T09:32:12Z Admin 1 /* June 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==June 2024== We might order a couple of eInk options to see if there is a cost-effective way to use 9 inch screens. More as things fold in. Also we publish a new [https://github.com/balthazar-space/balthazarKeyboardQMK/tree/main firmware for Balthazar keyboard] during this month. It will be adopted to a small OLED screens situated on the keyboard namely using SH1106 128x64 or SSD1306 128x32. Below is a working screen and the firmware implemented in QMK. <gallery> File:Oled.png File:Scr1.png </gallery> ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. <gallery> File:X230.jpg </gallery> ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. d353d4011676544813fb0c8f65611fc2d2339a5d 1022 1021 2024-07-01T12:52:47Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==July 2024== This month we will finish the last add-on - the external keyboard adapter as our last electronic part. The aim is to concentrate on our modular design and have industrial analysis of exsisting materials, concept development, 3 concept directions, selection of 1 refined design, engineering process, 3D surfacing, visuals for presentation, CAD file handover and visuals. Pictures of the following we will publish below as the progress goes on. ==June 2024== We might order a couple of eInk options to see if there is a cost-effective way to use 9 inch screens. More as things fold in. Also we publish a new [https://github.com/balthazar-space/balthazarKeyboardQMK/tree/main firmware for Balthazar keyboard] during this month. It will be adopted to a small OLED screens situated on the keyboard namely using SH1106 128x64 or SSD1306 128x32. Below is a working screen and the firmware implemented in QMK. <gallery> File:Oled.png File:Scr1.png </gallery> ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. <gallery> File:X230.jpg </gallery> ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 2caa76c489019dea0b7ada2555d2ee9bb42f1b21 1023 1022 2024-07-02T08:56:17Z Admin 1 /* July 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==July 2024== This month we will finish the last add-on - the external keyboard adapter as our last electronic part. The aim is to concentrate on our modular design and have industrial analysis of exsisting materials, concept development, 3 concept directions, selection of 1 refined design, engineering process, 3D surfacing, visuals for presentation, CAD file handover and a real tangible working prototype. Pictures of the following we will publish below as the progress goes on. ==June 2024== We might order a couple of eInk options to see if there is a cost-effective way to use 9 inch screens. More as things fold in. Also we publish a new [https://github.com/balthazar-space/balthazarKeyboardQMK/tree/main firmware for Balthazar keyboard] during this month. It will be adopted to a small OLED screens situated on the keyboard namely using SH1106 128x64 or SSD1306 128x32. Below is a working screen and the firmware implemented in QMK. <gallery> File:Oled.png File:Scr1.png </gallery> ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. <gallery> File:X230.jpg </gallery> ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. e11469a291bb63a1e3c5a58bfe913631b1f05d21 1025 1023 2024-07-11T16:30:42Z Admin 1 /* July 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==July 2024== This month, we will finish the last add-on, the external keyboard adapter, which is our final electronic component. The goal is to focus on our modular design and conduct an industrial study of current materials, idea development, three concept directions, selection of one refined design, engineering process, 3D surfacing, visuals for presentation, CAD file handover, and the creation of a tangible functional prototype. The picture below shows the latest PCB for an e[https://github.com/balthazar-space/Balthazar-Thinkpad-USB-adapter external ThinkPad keyboard adapter]: <gallery> File:PCB TP.png </gallery> ==June 2024== We might order a couple of eInk options to see if there is a cost-effective way to use 9 inch screens. More as things fold in. Also we publish a new [https://github.com/balthazar-space/balthazarKeyboardQMK/tree/main firmware for Balthazar keyboard] during this month. It will be adopted to a small OLED screens situated on the keyboard namely using SH1106 128x64 or SSD1306 128x32. Below is a working screen and the firmware implemented in QMK. <gallery> File:Oled.png File:Scr1.png </gallery> ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. <gallery> File:X230.jpg </gallery> ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 6b4eb557fcf1e567dcb35e826801f982e6aa7a31 1026 1025 2024-07-11T16:32:12Z Admin 1 /* July 2024 */ wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==July 2024== This month, we will finish the last add-on, the external keyboard adapter, which is our final electronic component. The goal is to focus on our modular design and conduct an industrial study of current materials, idea development, three concept directions, selection of one refined design, engineering process, 3D surfacing, visuals for presentation, CAD file handover, and the creation of a tangible functional prototype. The picture below shows the latest PCB for an e[https://github.com/balthazar-space/Balthazar-Thinkpad-USB-adapter xternal ThinkPad keyboard adapter]: <gallery> File:PCB TP.png </gallery> ==June 2024== We might order a couple of eInk options to see if there is a cost-effective way to use 9 inch screens. More as things fold in. Also we publish a new [https://github.com/balthazar-space/balthazarKeyboardQMK/tree/main firmware for Balthazar keyboard] during this month. It will be adopted to a small OLED screens situated on the keyboard namely using SH1106 128x64 or SSD1306 128x32. Below is a working screen and the firmware implemented in QMK. <gallery> File:Oled.png File:Scr1.png </gallery> ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. <gallery> File:X230.jpg </gallery> ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. 7ebb3b2fd96ac1654b38d727c4c96674aa45d981 1027 1026 2024-09-09T04:04:27Z Admin 1 wikitext text/x-wiki __NOTOC__ == Actual news and a Balthazar development progress == A short history of Balthazar: Development of Balthazar as a possible and realistic device has started at the end of April 2019 as a result of the long sessions that lasted a bit more than a few weeks of conferencing and emailing while discussing "whitepapers" content and realistically putting it into the context with the various sides involved. <br> We have talked to various people, representatives and teachers in '''MIT''', '''SiFive''', '''TUFTS''', '''Bauhaus''' University in Weimar and '''LEGO''' on a joint support in creating a working committee and a case for '''Balthazar'''.<br> '''Balthazar''' as a name for a laptop draws its associations from the ''Three Wise Man'' known as a ''Magus from Babylon'' and a ''Professor Balthazar'', a 1970's cartoon character that creatively solves problems in cooperative and inventive ways, being helped out by picturesque early depiction of an '''AI''' machine, "Veronica", in a process.<br> The conclusion was that the Balthazar laptop has to be a magical and beautiful personal computing device incorporating ethos, cooperative, inventive, and innovative characteristics as a combination of those two historical characters whether they were real or drawn. Timeline: ==September 2024== With a new "season" started and holidays fading away we are again back to work solving the final 3 designs, of which the one that we might adopt, weighting pros and cons, as a final and have the whole project ready for production. Also some testing of the modules and freshly awaited RiscV SoM are making this month a busy one. ==August 2024== In August things were getting slow, as usual. We have challange to put it all into the final design. And some friends are helping out there with solutions and their vision. ==July 2024== This month, we will finish the last add-on, the external keyboard adapter, which is our final electronic component. The goal is to focus on our modular design and conduct an industrial study of current materials, idea development, three concept directions, selection of one refined design, engineering process, 3D surfacing, visuals for presentation, CAD file handover, and the creation of a tangible functional prototype. The picture below shows the latest PCB for an e[https://github.com/balthazar-space/Balthazar-Thinkpad-USB-adapter xternal ThinkPad keyboard adapter]: <gallery> File:PCB TP.png </gallery> ==June 2024== We might order a couple of eInk options to see if there is a cost-effective way to use 9 inch screens. More as things fold in. Also we publish a new [https://github.com/balthazar-space/balthazarKeyboardQMK/tree/main firmware for Balthazar keyboard] during this month. It will be adopted to a small OLED screens situated on the keyboard namely using SH1106 128x64 or SSD1306 128x32. Below is a working screen and the firmware implemented in QMK. <gallery> File:Oled.png File:Scr1.png </gallery> ==May 2024== Dedicated to redesign the external keyboard extension PCB to fit in the housing. Also the issue is to build USB-C connector on the one-way channels on the forked ThinkPad external keyboard. <gallery> File:X230.jpg </gallery> ==April 2024== We await for a few new CM modules among those is Raspberry 5 CM too. There are some more CM RiscV boards coming but it is difficult to order those. Work for this and a few following month is to lay down the thin USB-C cables, fit those into the channels in the housing and designing the screen holders in place. THe overall housing might be smaller than envisaged 13" 3' diametar. ==March 2024== So we have the proper fit on the designing the cover for adopting external keyboard and right now figuring out our click-on PCB with a similar project - https://github.com/bluepylons/A-Thinkpad-USB-keyboard - a heavy lean on their design. We will be prototyping the PCB with smaller changes. Below we will post results in photo and also full description in our Wiki page. ==February 2024== This month we expect to have an add-on design to expand the choice with external and a proven keyboard from ThinkPad Lenovo x2XX series of laptops. Also, the frame to accommodate it in a fixed position. Progress in pictures will be, as per usual, below. <gallery> File:Fr1.png File:Fr3.png File:Fr4.png File:Fr5.png File:Fr8.png </gallery> ==January 2024== We started the new year with some progress and testing the Risc V various computing modules (CM) to see if we can rely on a certain solutions. Beagle, Milk/Mars CM, Orange. We have also scoured the web for the other's people experiences. General conclusion that RiscV is definitely improving and rapidly developing, but as far as the speed goes it still lags a certain stability. RP4 and the new RP 5 are both very fast and stable. RiscV still is not an ARM substitute, but it slowly gets there. A set of cards and some comparisons are shown below, as we continue testing. <gallery> File:Cm speed table.jpg File:RiscV clones-arm.jpg File:Cm compare.jpg </gallery> ==December 2023== Some new proposal for the keyboard that might be implemented, as it is interesting form factor and available as a custom-made. <gallery> File:KeyNewurh.jpg </gallery> ==November 2023== Still in the new design process, brings us to keep the 4 lower and upper modules, but the form factor is not be the same. Also Testing Beagle V ahead. So far it does look promising, not properly starting X widowing environment is the issue. ==October 2023== We expect to have some viable designs upcoming during this month. The development of an additional click-on chip for adding an external keyboard is in progress, and we will present it here. Searching for a producer for combined e-ink and OLED screen is in progress. OLPC style screen would be perfect for us. Also, bigger size than the original would be the best. More stuff upcoming soon. ==September 2023== This month we will develop and present later a couple of proposals for the final housing case design. Idea is to keep the modularity inside out. Also BeagleV Ahead a RISC V based boards are expected to be delivered, so we can test those with our modular set up. We will be looking into some inovative screens based on e-Ink. Still, an OLPC style screen that is a combination of the both worlds would be great to have. A new web site is in design and soon(ish) we will try to put it up. This Wiki stays up as a main source of info and the development until then. ==August 2023== This month we have ordered, for testing our modules a [https://www.beagleboard.org/boards/beaglev-ahead BeagleV] board. Once in we will test it with our Unifying board. Eagerly awaiting for this RiscV solution to see if it accomodates our needs. We also started to work on a "proper" web site where we will link this developing Wiki to, but also introduce some more easier navigation and lot better UI experience. Our case is slowly starting to take shape and we hope that in a 3-4 weeks we might be able to show an early version of our new design that will retain our principles of easy D-I-Y for the most of it. Some pictures again, are coming soon, and as we head towards the end of the year and with great hope we aim for final product to take its final shape and form. Also additional click-on chip for accommodating external replacement x2xx ThinkPad keyboards is being processed. In September we will see the results of the proposed new design. The aim is to compartmentalise housing, for the ease of access and construction. ==July 2023== Working really hard over the past few months, we have some results on a stitch self printed casing technique. It is deprived of a design, but the intention is to solve the technical issues on the prinet. Our design is commng up in the coming weeks, probably after August or September. Since we managed to engage a professional designer that has a long history in the product design, we will publish the progress on the path to a final design. Pictures of a stiched casing and Balthazar's modules are below and on our [[Specifications|Specifications -> Case]] page with more pictures of construction of self printed and stitched elements and modules fitting in: <gallery> File:Bottom lap.png File:Lcd cover 1.png File:Lap 1.png File:Lap 2.png File:Lap 3.png File:Lap 4.png File:Lap 5.png File:Lcdcoverexpl.png </gallery> ==June 2023== Pictures will be coming soon of a modular connecton of the casing. A couple of design proposals are also to be ready durning this month. We are getting closer to have asystem for self printing the case - at least the mechanicals and correct measuraments. ==May 2023== A final design has been in the making, also the internal measurements and hinges developments with our external partners. We focus on the joining system to enable a self-printing to a whole unit to a screen dimensions. Soon the pictures will be posted here and some updated electronic add-ons such as click-on chip to accomodate a replacment keyboards from Think Pad X2xx series. Also included in an overall design will be a frame to securely set in such widely available keyboards. ==April 2023== With the other things still under the development, we fully concentrate to the design. Incoming are many proposals, from purely "hacker's" tool, mean looking military case, ThinkPad style case, plain black case with colorfull keys, normal not and proposed curved keyboard etc. Many ideas and wishes. We will try to see what is really doable. Every good design requires the time. ==March 2023== In march we will develop the pivoting system for screen attachment as in new hinging. Idea is to make it sturdy and robust, trying to see if that is doable as in DIY system. Some suggest for a a plastic, some aluminium one. Also adding the click-on chip to our Unifying board for adopting ThinkPad's keyboard series x2xx that seem could appeal to some users. That would also require additional casing frame adopted to accomodating such keyboard. ==February 2023== New system for joining toghether elements of casing has been devised and we are polishing the process. Pictures will be posted soon also how-to and DIY description. Also we start of the multisided approach to ergonomics and te final design. ==January 2023== And we enter the new year with the all the modules tested and debugged, with soon publishing all of the results and BoM. Plan is to concentrate on the casing and a concepts that we want to breing into Balthazar system. Slow but steady start accelerating towards the finalised system. ==December 2022== We are working very hard to test all the modules and see the screens fit as expected. Developing the case is taking a bit longer, and we wait to hear from our partners on solutions for closing – opening systems. Also for us, the ergonomic aspect of the case as in the whole laptop enclosure is under development. ==November 2022== Being rapidly approaching to our first working prototype working in a case and with a various display options, this month we will have finally a big milestone achieved. Naturally we will have to iron some issues with our modules, also addressing ergonomics, opening-closing system test designs and an overall aesthetic appeal shaped. Below is the first put together and a complete system with home 3D printer in a stitched together case. We also have new modules assembled as Balthazar Keyboard, Unifying Board (upgraded with Ethernet connector) and PSU and those are being tested. More to come soon on our [[Documentation]] and [[Instruction Manual]] pages. <gallery> File:Proto complete.png File:Case modules seam.png File:Psu new.png File:Keyboard new1.png File:Unifying assembl.png </gallery> ==October 2022== During this month, we will debug and solve the issues ([https://github.com/balthazar-space on GitHub]) we encountered during the tests and setting prototype Balthazar system. Ambition is to have fully debugged, new versions and fully assembled PCBs with no or lot less issues. We can put in tests and present it as a working prototype, hopefully at the end of this month. Doing it this way, it'll make the whole platform more stable and easier to build. The status of those will be updated here as we progress. Debugging and issues tracing on Unifying board. <gallery> File:Unifyingv.2.png File:Unifying v02 top.png File:Unifying v02 bottom.png </gallery> After switching to 4 layer - PSU board needs rerouting. <gallery> File:Psuv03.png File:PSU3 top v02.png File:PSU3 bottom v02.png </gallery> Case design and set up with batteries, keyboard, PSU/I/O and Unifying board. <gallery> File:4.png File:5.png File:7.png File:8.png </gallery> You can also see the 3D model of our upcoming prototype and have a preview. Some elements are still developed, such as open-closing hinge system that we will try to implement, but the overall implementation is progressing. What for us is very important is to have proper dimensions and an internal set-up for modules with a proper module fit. A mock-up case versions are in print, and early next month we will post a video of all the modules working in the housing with a screen. Please click -> [https://skfb.ly/ozF6W here] and -> [https://skfb.ly/ozF7w here] and rotate the case and see for yourself. Naturally improvements in ergonomics and aesthetics will be implemented as we go on. Also below is a print of a case required while adjusting internal dimensions with new debugged modules. Those are ready to be assembled and implemented into the case. <gallery> File:Case print1.png File:Key new.png File:Unifying new.png File:PSU new.png </gallery> ==September 2022== Working hard on modules here are some pictures that will be followed up by videos of assembly on our [[Documentation#Keyboard|production and assembly]] page. We have encountered some issues addressed on our [https://github.com/balthazar-space GitHub] page, and we are working to rectify those. <gallery> File:4 unify.jpg|thumb| File:HDMI display.jpg|thumb| File:3 unify.jpg|thumb| </gallery> ==August 2022== There are modules being produced and tested during August and we will post the results. Also publishing those pictures when ready and also testing results. ==July 2022== We have our modules in production as "alpha" prototypes. First to be ready and followed its [[Documentation#Keyboard|production and assembly]] is our modular keboard module. A shortage of certain elements is a bit frustrating, but we manage to follow up. ==June 2022== We are developing the final [https://github.com/balthazar-space/case-and-design case design], also creating [[Documentation|documentation]] and [[Instruction Manual|instruction manual assembly]]. All modules are now in delivery and a production to be put in a real working prototype. It will take some time to assemble and show in a video a real “alpha” working prototype, but mostly all our PCBs and other adjoining elements are ready. We have also updated our [https://github.com/balthazar-space Github] pages with [https://github.com/balthazar-space/case-and-design/tree/main/images/production_design_images new design and images] of the [[Specifications|case]]. And here are PCB modules that we received, Unifying board, keyboard and PSU are produced. Those are ready to be built and connected to a working state, also as it is envisaged in the case layout. Keyboard is being assembled. More pictures of interconnected PCBs to come real soon. In the meantime, in the gallery below there are also tests of Balthazar's modules, screen, and a keyboard working with RP3. Production process of separate modules are to be found on our [[Documentation]] page, updating regularly and as things progress. <gallery> File:Keyboard prod.png File:Balt unify.png|thumb| File:Balt keyboard.png|thumb| File:Balt PSU.png|thumb| File:Balt.png|thumb| File:Balt 1.png|thumb| File:Balt work10.png|thumb| File:Balt work9.png|thumb| File:Balt-work11.png|thumb| </gallery> ==May 2022== We will develop, once when ready, the final case design into rapid prototyping print-outs so we can have it 3D printed and ready for connecting and testing. Documentation and some nice new animations and drawings will be done. ==April 2022== Ordering all of the PCB pre-prototypes to construct first working models in various combinations. There are some issues with chips supply chain, but we do hope we can adopt. Also we are working fast towards clear design and positioning inside the case. ==March 2022== The major design of Unifying PCB has started and we design it to be an expansion and a crucial element to our device. It enables Compute module sized cards to be sandwiched on, giving some reasonable expansion abilities to Balthazar. Also we modified, debugged and updated all our previous modules. ==February 2022== We did a third version of our ergonomic laptop keyboard, still updating QMK and adding features. It is already on our [https://github.com/balthazar-space GitHub] page. There we also have a preliminary Unifying HAT board. It is done as a basic in its design, but we need to complete BoM and adjoining the documentation. This is due during this month or at least early next month. Issues with the case design we are solving on the go and waiting for final precise dimensions. ==January 2022== Starting the third year of Balthazar's development while getting preliminary case designs soon to be published on our GitHub page. Also, we are sorting out and updating all the documentation on a GitHub. We are also readying the third iteration of a keyboard with standard slim Cherry style click switches. Ports and I/O HAT-on module is still being deep in the design process. We are lacking many options there and are forced on changing basic design due to the continuous shortage, lack of a wide availability and a narrowed choice of chips. But, we will definitely get there. ==December 2021== We started to design a HAT module that will accomodate any standardized HAT-on CPU such as FPGA based such as ULX3S, ULX4M or Raspberry Pi Compute module, or any ther SoM, lining a groundwork to equip or co-CPU Balthazar with emulated cores of user's choice and also have better GPIO bridge to connect to cameras, sensors, Arduinos, synthesizers or any other IoT "things". ==November 2021== While design of the housing is being developed, we concentrate and work to get ready for all the internal elements. That includes battery, I/O power module, keyboard gets proper Cherry slim switches. We also see that to get towards designing HAT module we need to redesign back and upper right corner of the housing - also there is an idea to accomodate ThinkPad's keyboards for up to models series X2xx. QMK software is being updated and upgraded to a fully working version to accompany our secure keyboard. ==October 2021== We work hard on developing the proper multimodal housing, choosing natural, recyclable materials. So the primary focus starting this month also for some time to come, is on pure design, aesthetics, haptics, colours, look, and feel. Very soon a new website connected to this wiki will be done for better communication to a wider public and decision-makers. 10, 20, 30 — no less, but no more. As we partner along with [https://radiona.org/ Radiona] from Zagreb, Croatia, and will design and produce an extension board based on [https://radiona.org/ulx3s/ FPGA ULX3S] as our main coprocessor, we will also produce all our modules with them. Probably we will opt for a more capable chip there, but it remains to be seen. Exciting stuff, nevertheless. On the other front of various security issues and how to really trust the devices, we also talk to some SmartCard solution that would be inexpensive to build in/on and would bring Balthazar closer to a really trusted device. Also, Alibaba rocks as always, so we follow their [https://github.com/T-head-Semi RISC-V from T-Head Semiconductor Co., Ltd.] chips. ==September 2021== We have committed to cooperation with rapid prototyping and PCB design [http://www.radiona.org Radiona] makers place from Zagreb, Croatia. The [https://www.hackster.io/radiona/ulx3s-project-f946c2 ULX35 ] FPGA is in one way or another going to be added to our I/O board in form of a co-processor expansion to better handle GPIO, add WiFi and BlueTooth, and some other funky stuff like Amiga and C64 retro gaming, RISC-V cores, some rudimentary Linux and lots of other cool stuff. Also with the help of [https://radiona.org/ Radiona], we will develop the "add_the_other_keyboard" module board - the idea there is to have compatibility with the ThinkPad series way up to the model X230 since those keyboards are rather inexpensive, they perform well and are plenty of on the market. ==August 2021== In August we have bundled our modules, keyboard and screen together and got them pretty much a working system running on NanoPi from OpenPi, Raspberry Pi 4, Odroid and Beagleboard. QMK software needs polishing a bit, also a small OLED screen for the keyboard we now need to test and to opt for the best solution. So far we are happy with how it looks (but we will need to work on a better versatile casing/housing design) and how it all performs. ==July 2021== Technical drawings are done for moulding/cutting and we will collect and choose a final candidate for speakers, mic and camera. Also, a keyboard will get its final QMK file with an early password entry system enabling boot into OS. Still waiting for RISC-V boards to be delivered. EU laws are now in full force of delaying and taxing imports prolonging delivery times, meanwhile, we search for other options - dreaming of a European chip supply. ==June 2021== We have done CNC/3D pre-prototype case elements getting to the phase where we can incorporate the screen and all the modules in. Also during the next few weeks, we will look into options having those mass-produced - choice of materials being most focused on. Happy with the overall progress, we now are closing in on finishing the design, colouring scheme, ergonomics of the keyboard functionalities and if not final then close to the final QMK files. The Prospect of having a real RiscV SoM running full-stack Linux is coming closer and we will also work on that making sure everything fits and works together. ==May 2021== While at the final construction and the design approach we try to fix some issues with connecting external modules. Also, we wait for the response on [https://beaglev.seeed.cc/ StarFive] SoM that we might find as a first choice in the scarce market of RiscV SoMs. ==April 2021== The first casing elements were printed/CNCed. We need to pair and align them, determine proper screw holes, see that cooling is viable without the fan, see that cabling is neat and practical. This is the last of the pre-production design phase and we seek quality and simplicity. ==March 2021== We got both I/O USB and keyboard modules working and paired with a screen panel that we would use. Screen panels are tested and those seem like a good choice. QMK firmware is getting the last check-up and will be soon done and uploaded on our Github, however, there was a temporary lack of chips that we want to use, so we are running a bit later than expected - we are trying to catch up so we can move to another phase - which is to decide on a final housing design and hinge system. We have some mock-up layouts and speakers and touchpad layouts and internals. ==February 2021== We made a preliminary mockup with positioning PCBs into the first proper dimensions within the housing and now we basically can see the whole Balthazar slowly coming to a shape. When QMK firmware is finished and tested we will upload it to Github. Expected in this month is to have first screenshots of an interconnected keyboard, power supply, I/O USB, screen and password input before the boot into the system is done in QMK. ==January 2021== Power supply and I/O USB PCBs came in a bit later than expected, but that was fine as we were busy with QMK firmware and perfecting our keyboard. The screen is being mounted into the prototype frame with the hinges, also tested for resolution. We had borrowed 3rd party HDMI PCB drivers for testing the whole system using Raspberry Pie 4 and some other more open similar modules. ==December 2020== We wait for the first batch of PCBs that is merged into one - the power supply and I/O hub - as a single test module. Keyboard PCB is now in the testing phase and we will publish the results. While there are no real issues encountered in the first testing and firmware setting phase, we also wait for the silicone cover keys, but we were told that it might take time until we get our hands on it. Housing is getting milled, changing and adopting minor dimensional changes and so far we are also rather happy with the preliminary results and overall achieved dimensions. Also, a rather good choice is made on the speakers and a camera/mic module, so those are ordered as we wait for the packages. ==November 2020== Screens arrived and also some of the PCBs are on the way back to us. There is a preliminary casing being drilled and milled and also a hinge system looked into with few simple yet robust solutions underway. Soon we will publish photos and a first look at the casings and the other possible designs we play with and about. Also, the tests and results of our freshly arrived [[Keyboard|keyboard PCB]] and adjoining prototype modules will be published. ==October 2020== We have continued the development of a unified PCB that will serve as a hub to support various additional Systems-on-Module delivering power and all the I/O connectors needed. Also, we still wait for the first batch of prototypes of 2 PCBs and a special keyboard PCB. On those, we think also in merging those into the one as it will reduce the costs. Very soon we will have the first bottom chassis CNC-ed housing and cabling designed and incorporated into CNC housing. Screens are on the way as we have ordered various resolutions and types. We need to evaluate those first and see the larger batch availability and that depends also on our production partners. We do expect to have all those PCB received and tested during the end of this or the following month. ==September 2020== We have ordered a couple of screens that we might want to test and choose the one to use. Also, we will be travelling to Italy and Spain to meet with our development partners to discuss some aspects of the design and some clearance in the technical solutions. After mid-September, we expect to have the housing case and its elements and get all the PCBs ready for fitting and testing. We also look now into the options of some SoM to use for testing the modular elements. During the next couple of weeks, we intend to CNC some crucial parts of the housing from plastic and aluminium, adjusting the external and internal dimensions of built-in elements. Naturally, photos and detailed descriptions, with all the results and measurements will be published here. ==August 2020== While waiting for PCB samples to arrive we have been working on a few 3D models and overall designs for the housing. Also, we started to design further PCBs to accomplish and complete the innards of Balthazar. We will try during August and early September to CNC some possible designs and see what would be the best fit. Also in the coming weeks, we will look into the screens that we might want to use. ==July 2020== We had a short summer break. PCBs are back-ordered and now we are waiting for the prototype boards to be made and arrive apparently in late August. Also, we will see into the camera, speakers and other peripherals and order a few samples to test and see what would be the best possible fit as a prototype. ==June 2020== June is a revision month and we are applying to FSF for a check-up on our hardware compliance, also the first breadboard/prototypes will be made. And we are going to start working on the overall design incorporating also CNC prototype of housing with a fitting keyboard and a space for other modules. ==May 2020== May has started with finishing the designs for the I/O hub and a board that will enable a connection to our keyboard and power supply. [[I/O_USB|I/O USB ]] page was set up and files were ready to publish. We now have three original PCBs freely downloadable and ready for prototyping. ==April 2020== It has been one year that our idea has been born. We have opened a [https://github.com/balthazar-space/balhazar Github] page with KiCad files ready to download. Also, our licence is now CERN OSHW instead of GNU v3.0. There we will be updating files and all our "deliverables". In March and continuing this whole month we have started to develop an I/O USB board and work on it to deliver files for our internal I/O USB docking board for the keyboard, power supply, camera, microphone, somewhere in mid-May. ==March 2020== Two PCBs keyboard and a power supply are ready real soon, we aim at or around March 15th and we will upload all the relevant data and files. So thereafter bit of C-19 crisis delay as we were caught with a quarantine we have delivered both PCB designs and schematics also worked towards opening a Github page. ==February 2020== We have started to develop 2 PCBs - a keyboard and a power supply. It is expected to be ready in a month also with PCB schematics, a Bill of materials and design guidelines. ==January 2020== With New Year comes also the new prospect of cooperation with [http://slimbook.es Slimbook] - a pure Linux laptops manufacturer from Spain. We are researching to see how we can incorporate our design proposals and align to have a joint development. We have also released the power supply concepts, looked into the price and the availability of the parts for it and started our encrypted keyboard PCB development. Also, schematics and PCB for the overall "modular upgradeability and add-on" concept is in development. ==December 2019== Some case design proposals are now in and we evaluate those, as we met with a few '''LEGO''' design people and got a good insight into plastic casing designs and heat issues. Also, hinges are a bit of an issue, but till the end of the year, there will be some viable solutions. We prepare the 2-day meet-up in Weimar, somewhat later than anticipated, but will happen in the next 2 weeks provided that all steering members can commit to attending. As it is an end to one very exciting year, we work hard towards having everything ready before the holidays. Some boards are in and received and some are still coming, so with the help of '''Armbian''' team, we will see and choose what the best options are there. Also thanks to '''IBM''' 's Open Sourcing move in '''Power9''' ISA field, we started to look hard into that direction, too. ==November 2019== Somewhat longer emailing between SiFive and us on adopting '''RISC-V''' and '''ISA''' making it work with GPUs. We met with '''Armbian''' people that might help us with setting up RISC -V build tools and work deeper on HW encryption. Visited '''Tipro''' a well known European custom and industrial keyboard company with proposals and basic HW design and software. Keyboard's design and FW driven bus we will base on smaller ''' RISC-V''' controller for bus-to-motherboard encryption and we will work on it together over the coming months. We have drafted a mutual agreement to publish it all publicly under '''CERN/GPL3''' licences, more to confirm on that later in the year. More serious RISC-V development boars namely Freedom Unleashed are ordered and those are on the way, as well as a few of ''' EOMA68''' evaluation boards. We are also off to Denmark, Billund to meet with Moulding people from '''LEGO''' and also brief some representatives of '''LEGO Education''' on our current development. In the Weimar end of November latest mid-December at the Bauhaus Uni, we will gather in a formal first meeting with steering committee members and set the strategy and a path for the next few months of accelerated development. We are looking into '''CrowdSupply''' support and options we have there. One thing we do know for sure is - we do not want to over-promise. ==October 2019== We did the first renders and a few design studies of the casing, but more we will discuss with '''LEGO''' Moulding people in December. Also, some 2D and 3D drawings were made, still to be detailed before it goes to the CNC alpha case phase. Presented project by mailing a Turkish high-quality moulding company that is specialised in "electronic enclosures" for internal plastics and guidelines, cooling etc. Collected and decided on a few software models that are Open Source and rather powerful when combined. A German screen and eInk company was questioned for a second screen choice, with our requirements. Looks good, so far. We also got support from '''NLNET''' in a shape of technical support and a financial donation to speed up R&D and come up with tangible prototypes faster. What a great push that is. ==September 2019== A second public presentation, this time at an even more appropriate event, was made in Venice, Italy, during the '''ESC - End of Summer Camp''' where advanced computer and internet users, some HW developers, as per default, offered their participation in various aspects of development. An enthusiastic and very knowledgeable crowd. We collected ourselves an old and new bunch of Linux capable boards that we used over the years, some new micro-computers, SoC's and SoM's and started looking into software features and encryption modes and options that we can make use of it. Keyboard design and a ''secure keyboard to motherboard concept'' was done, even more drawings were made and put up for UI and UX also for the proposed educational interface. We talked with '''HiTechic''' again on the development of a secure USB dongle and GPIO boards design and they gave us an estimate and some overview of expectations for prototypes. Power supply design requirements are made and also battery and other issues (magnetic vs. mechanical switches etc.) were worked on until we all agreed on how what and when. ==August 2019== prepared a primary presentation, description and imaginary nice to have specs and a Bill_Of_Materials. A first semi-public presentation was held at the end of August on premises of '''Bauhaus University''' in Weimar to a working group consisting of 30 + Master and Bachelor students of Media Systems and with the help of ''Charles Wuetrich'' and his Chair for Computer GFX. There were tons of questions in the discussion and some valuable points were incorporated into the further strategy of the development. ==July 2019== All the security wish-features were added to our whitepaper style webpage, professor Chris Rogers from '''TUFTS''' helped us to make the case in educational aspects of Balthazar, HiTechnic's owner Steve Barker gave his views in designing and building Balthazar with tons of useful tips and contacts. Michael Anderson, ex-LEGO electronic engineer and HW designer guided some technical decisions sharing his production knowledge experience. We also applied for some minor external funding to '''NLNET''', as it is not easy to make a new approach in designing the laptop investing just our financial resources. ==June 2019== A concept for a form factor came up and the first drawings and sketches were made. Deep dive into RISC-V ISA and foresight of viable future processors came up. Keyboard design was in the making, also thorough research was carried on, under the wise guidance especially in some technological approaches of EOMA68 developer Luke Kenneth Casson Leighton. That collaboration gave us some useful tips and helped us to find good reasons not to reinvent the hot water. We won't. ==May 2019== started preliminary talks to Tripodo started on Intellectual Property licences and issues for a famous XO PixelQi screen with a dimmable backlight and sun-readable features. That is still pending. The domain is registred and a website goes up with a rather white-paper content leaving an input open for contributors that came from all sides. ==April 2019== a day Zero, where we realised that it can be done, it should be done and we even kind of knew how-to. fd7ed2b86ed977890300d8166a9958f9547c285d 6 266 1017 2024-06-26T10:27:57Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 267 1019 2024-06-27T07:07:18Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 268 1024 2024-07-11T16:29:24Z Admin 1 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709